Locating and organizing digital receipt data for use in in-store audits

ABSTRACT

The present invention extends to methods, systems, and computer program products for auditing in-store sales transactions when a digital receipt is issued. A receipt application server formulates a digital receipt from digital receipt data received from a POS system. The digital receipt is sent from the receipt application server to an auditor mobile device at the location of the POS system. A human auditor can view the digital receipt during an in-store audit. In some embodiments, one or both of the receipt application server and the auditor mobile device reorder receipt entries so that items having specified characteristics are presented more prominently on a display. For example, receipt entries can be re-ordered such that higher profit margin items, bulkier items, or more likely to be stolen items are presented more prominently. As such, a human auditor is more likely to expressly audit these types of items.

BACKGROUND

1. Field of the Invention

This invention relates generally to the field of electronic salestransactions, and, more particularly, to locating and organizing digitalreceipt data for use in in-store audits.

2. Related Art

In a variety of transactions, customers or buyers of goods or servicestypically receive receipts from their respective merchants or serviceproviders as proof of existence of conducted transactions. Generally,receipts are issued by merchants and service providers for a number ofreasons including, for example, regulatory or tax reasons andconvenience purposes. A receipt provides information about acorresponding transaction for the purpose of providing all participantswith a trace or record of the transaction. Receipts can later be used bya consumer for various purposes including, for example, provingparticipation in a transaction for tax reporting purpose, productreturns, use as a claim ticket for a further transaction, provisioningwarranties, etc. Merchants can issue receipts to a customer in digitaland/or paper format.

Some merchants also audit customers on exit to mitigate shoplifting,check for cashier errors, etc. To conduct an exit audit, a human auditorreviews items in the customer's cart, sack, etc. and compares items inthe customer's possession to items listed on the customer's receipt toverify that items were indeed purchased.

A number of factors limit the amount of time that can be allocated forauditing an individual customer. For example, depending on the number ofauditors, how busy a store is, a merchant's desire to allow customers toefficiently exit a store, etc. a human auditor may have from a fewseconds up to a minute to audit each individual customer. Due at leastin part to these time limitations, a human auditor typically verifiesonly a few items at most when conducting an exit audit for a customer.

Since a few items at most are verified, exit audits often producemarginal results. Items on a receipt can be listed in a random order(e.g., the order the cashier scanned the items) making it difficult fora human auditor to efficiently verify an item was purchased. As such,items that are less important to audit, for example, cheaper items orlower profit margin items may be listed on parts of the receipt that aremore efficient for a human auditor to view (e.g., near the top, on thefirst page, etc.). On the other hand, items that are more important toaudit, for example, more expensive items, higher profit margins items,or items with increased likelihood of being stolen may be listed onparts of the receipt that are less efficient for a human auditor to view(e.g., in the middle or bottom, on subsequent pages, etc.). When it isless efficient to view important items, fewer important items can beaudited in an allotted time. Thus, an exit audit may verify the purchaseof at least some cheaper or lower profit margin items at the expense ofoverlooking more expensive items or items that are more likely to bestolen.

Further, exit audits are also somewhat annoying and intrusive tocustomers. A customer may wait in one line to checkout. After checkout,the customer may find they have to wait in another line to get audited.When a human auditor is eventually reached, the customer is asked toproduce a receipt. The customer must then wait while the auditorverifies items in a cart, sack, etc. against the produced receipt.

Audits based on digital receipts can be even more intrusive to acustomer and also more difficult for a human auditor to conduct. Forexample, to conduct an audit based on a digital receipt, the auditor mayrequest to view the digital receipt on a customer's mobile device (e.g.,a mobile phone). This is intrusive to the customer as they are beingasked to show the contents of their mobile device to a stranger. It mayalso be that the mobile device the digital receipt was sent to is not inthe customer's possession, has a dead battery, etc.

If a digital receipt is presented, a human auditor may be able to viewthe digital receipt only for a moment and then must verify items fromthe digital receipt. Further, a mobile device may lack sufficient screensize to display an entire digital receipt at once. Thus, only a portionof a digital receipt may be visible on the mobile device when shown tothe human auditor. User interaction (e.g., scrolling to a next page,etc.) may be required for other portions of a digital receipt to bedisplayed. However, the mobile device is property of the customer. Assuch, the human auditor has no right to take possession of the mobilephone to access other portions of the digital receipt. Thus, the humanauditor has to perform an audit based on viewed items, which may lessdesirable items to audit relative to other items.

Further, many states in the United States do not require a customer toprove that they have purchased anything. As such, a customer may refuseto comply with a request to hand over a receipt or provide a view of areceipt.

BRIEF DESCRIPTION OF THE DRAWINGS

The specific features, aspects and advantages of the present inventionwill become better understood with regard to the following descriptionand accompanying drawings where:

FIG. 1 illustrates an example block diagram of a computing device.

FIG. 2 illustrates an example computer architecture that facilitateslocating digital receipt data for use in in-store audits.

FIGS. 3A and 3B illustrate a flow chart of an example method forlocating digital receipt data for use in in-store audits.

FIGS. 4A and 4B illustrate an example computer architecture thatfacilitates locating and reordering digital receipt data for use in anin-store audit.

FIGS. 5A and 5B illustrate a flow chart of an example method forlocating and reordering digital receipt data for use in an in-storeaudit.

FIGS. 6A and 6B illustrate an example computer architecture thatfacilitates locating and reordering digital receipt data for use in anin-store audit.

FIGS. 7A and 7B illustrate a flow chart of an example method forlocating and reordering digital receipt data for use in an in-storeaudit.

FIGS. 8A and 8B illustrate an example computer architecture thatfacilitates reordering and locating digital receipt data for use in anin-store audit.

FIGS. 9A and 9B illustrate a flow chart of an example method forreordering and locating digital receipt data for use in an in-storeaudit.

FIG. 10 illustrates an example schematic block diagram of apoint-of-sale (“POS”) system.

FIG. 11 illustrates an example schematic block diagram of a network ofpoint-of-sale (“POS”) systems.

DETAILED DESCRIPTION

The present invention extends to methods, systems, and computer programproducts for locating and organizing digital receipt data for use inin-store audits. In the following description of the present invention,reference is made to the accompanying drawings, which form a parthereof, and in which is shown by way of illustration specificembodiments in which the invention is may be practiced. It is understoodthat other embodiments may be utilized and structural changes may bemade without departing from the scope of the present invention.

Embodiments of the present invention may comprise or utilize a specialpurpose or general-purpose computer including computer hardware, suchas, for example, one or more processors and system memory, as discussedin greater detail below. Embodiments within the scope of the presentinvention also include physical and other computer-readable media forcarrying or storing computer-executable instructions and/or datastructures. Such computer-readable media can be any available media thatcan be accessed by a general purpose or special purpose computer system.Computer-readable media that store computer-executable instructions arecomputer storage media (devices). Computer-readable media that carrycomputer-executable instructions are transmission media. Thus, by way ofexample, and not limitation, embodiments of the invention can compriseat least two distinctly different kinds of computer-readable media:computer storage media (devices) and transmission media.

Computer storage media (devices) includes RAM, ROM, EEPROM, CD-ROM,solid state drives (“SSDs”) (e.g., based on RAM), Flash memory,phase-change memory (“PCM”), other types of memory, other optical diskstorage, magnetic disk storage or other magnetic storage devices, or anyother medium which can be used to store desired program code means inthe form of computer-executable instructions or data structures andwhich can be accessed by a general purpose or special purpose computer.

A “network” is defined as one or more data links that enable thetransport of electronic data between computer systems and/or modulesand/or other electronic devices. When information is transferred orprovided over a network or another communications connection (eitherhardwired, wireless, or a combination of hardwired or wireless) to acomputer, the computer properly views the connection as a transmissionmedium. Transmissions media can include a network and/or data linkswhich can be used to carry desired program code means in the form ofcomputer-executable instructions or data structures and which can beaccessed by a general purpose or special purpose computer. Combinationsof the above should also be included within the scope ofcomputer-readable media.

Further, upon reaching various computer system components, program codemeans in the form of computer-executable instructions or data structurescan be transferred automatically from transmission media to computerstorage media (devices) (or vice versa). For example,computer-executable instructions or data structures received over anetwork or data link can be buffered in RAM within a network interfacemodule (e.g., a “NIC”), and then eventually transferred to computersystem RAM and/or to less volatile computer storage media (devices) at acomputer system. RAM can also include solid state drives (SSDs or PCIxbased real time memory tiered Storage, such as FusionIO). Thus, itshould be understood that computer storage media (devices) can beincluded in computer system components that also (or even primarily)utilize transmission media.

Computer-executable instructions comprise, for example, instructions anddata which, when executed at a processor, cause a general purposecomputer, special purpose computer, or special purpose processing deviceto perform a certain function or group of functions. The computerexecutable instructions may be, for example, binaries, intermediateformat instructions such as assembly language, or even source code.Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the described features or acts described above.Rather, the described features and acts are disclosed as example formsof implementing the claims.

Those skilled in the art will appreciate that the invention may bepracticed in network computing environments with many types of computersystem configurations, including, personal computers, desktop computers,laptop computers, message processors, hand-held devices, multi-processorsystems, microprocessor-based or programmable consumer electronics,network PCs, minicomputers, mainframe computers, mobile telephones,PDAs, tablets, pagers, routers, switches, various storage devices, andthe like. The invention may also be practiced in distributed systemenvironments where local and remote computer systems, which are linked(either by hardwired data links, wireless data links, or by acombination of hardwired and wireless data links) through a network,both perform tasks. In a distributed system environment, program modulesmay be located in both local and remote memory storage devices.

Embodiments of the invention can also be implemented in cloud computingenvironments. In this description and the following claims, “cloudcomputing” is defined as a model for enabling ubiquitous, convenient,on-demand network access to a shared pool of configurable computingresources (e.g., networks, servers, storage, applications, and services)that can be rapidly provisioned via virtualization and released withminimal management effort or service provider interaction, and thenscaled accordingly. A cloud model can be composed of variouscharacteristics (e.g., on-demand self-service, broad network access,resource pooling, rapid elasticity, measured service, etc.), servicemodels (e.g., Software as a Service (SaaS), Platform as a Service(PaaS), Infrastructure as a Service (IaaS), and deployment models (e.g.,private cloud, community cloud, public cloud, hybrid cloud, etc.).Databases and servers described with respect to the present inventioncan be included in a cloud model.

Further, where appropriate, functions described herein can be performedin one or more of: hardware, software, firmware, digital components, oranalog components. For example, one or more application specificintegrated circuits (ASICs) can be programmed to carry out one or moreof the systems and procedures described herein. Certain terms are usedthroughout the following description and Claims to refer to particularsystem components. As one skilled in the art will appreciate, componentsmay be referred to by different names. This document does not intend todistinguish between components that differ in name, but not function.

In general, embodiments of the invention are directed to locating andorganizing digital receipt data for use in in-store audits. Upon theclose of a customer sales transaction at a location, digital receiptdata for the sales transaction is sent to a receipt application serverfor storage. The receipt application server formulates a digital receiptfrom the digital receipt data. The digital receipt is subsequently sentfrom the receipt application server to an auditor mobile device at thelocation (and possibly also to customer mobile device). Receipt entriesfrom the digital receipt can be presented at the auditor mobile device.A human auditor can view the presented receipt entries at the auditormobile device and match the digital receipt to the customer. The humanauditor can also use the displayed receipt entries (as well as otherreceipt entries contained in the digital receipt) to audit customermerchandise upon the customer exiting the location.

In some embodiments, receipt entries contained in a digital receipt arere-ordered for presentation at the auditor mobile device. Re-orderingcan occur at the auditor mobile device and/or at the receipt applicationserver based on audit rules. The audit rules can be stored at theauditor mobile device or at the receipt application server. Receiptentries can be re-ordered such that receipt entries for items havingspecified characteristics are presented more prominently (e.g., at thetop, highlighted, etc.). For example, receipt entries can be re-orderedsuch that higher profit margin items, bulkier items, or more likely tobe stolen items are presented more prominently. As such, a human auditoris more likely to expressly audit these types of items.

FIG. 1 illustrates an example block diagram of a computing device 100.Computing device 100 can be used to perform various procedures, such asthose discussed herein. Computing device 100 can function as a server, aclient, or any other computing entity. Computing device 100 can performvarious communication and data transfer functions as described hereinand can execute one or more application programs, such as theapplication programs described herein. Computing device 100 can be anyof a wide variety of computing devices, such as a mobile telephone orother mobile device, a desktop computer, a notebook computer, a servercomputer, a handheld computer, tablet computer and the like.

Computing device 100 includes one or more processor(s) 102, one or morememory device(s) 104, one or more interface(s) 106, one or more massstorage device(s) 108, one or more Input/Output (I/O) device(s) 110, anda display device 130 all of which are coupled to a bus 112. Processor(s)102 include one or more processors or controllers that executeinstructions stored in memory device(s) 104 and/or mass storagedevice(s) 108. Processor(s) 102 may also include various types ofcomputer storage media, such as cache memory.

Memory device(s) 104 include various computer storage media, such asvolatile memory (e.g., random access memory (RAM) 114) and/ornonvolatile memory (e.g., read-only memory (ROM) 116). Memory device(s)104 may also include rewritable ROM, such as Flash memory.

Mass storage device(s) 108 include various computer storage media, suchas magnetic tapes, magnetic disks, optical disks, solid state memory(e.g., Flash memory), and so forth. As depicted in FIG. 1, a particularmass storage device is a hard disk drive 124. Various drives may also beincluded in mass storage device(s) 108 to enable reading from and/orwriting to the various computer readable media. Mass storage device(s)108 include removable media 126 and/or non-removable media.

I/O device(s) 110 include various devices that allow data and/or otherinformation to be input to or retrieved from computing device 100.Example I/O device(s) 110 include cursor control devices, keyboards,keypads, barcode scanners, microphones, monitors or other displaydevices, speakers, printers, network interface cards, modems, cameras,lenses, CCDs or other image capture devices, and the like.

Display device 130 includes any type of device capable of displayinginformation to one or more users of computing device 100. Examples ofdisplay device 130 include a monitor, display terminal, video projectiondevice, and the like.

Interface(s) 106 include various interfaces that allow computing device100 to interact with other systems, devices, or computing environmentsas well as humans. Example interface(s) 106 can include any number ofdifferent network interfaces 120, such as interfaces to personal areanetworks (PANs), local area networks (LANs), wide area networks (WANs),wireless networks (e.g., near field communication (NFC), Bluetooth,Wi-Fi, etc, networks), and the Internet. Other interfaces include userinterface 118 and peripheral device interface 122.

Bus 112 allows processor(s) 102, memory device(s) 104, interface(s) 106,mass storage device(s) 108, and I/O device(s) 110 to communicate withone another, as well as other devices or components coupled to bus 112.Bus 112 represents one or more of several types of bus structures, suchas a system bus, PCI bus, IEEE 1394 bus, USB bus, and so forth.

FIGS. 2A and 2B illustrates an example computer architecture 200 thatfacilitates locating digital receipt data for use in in-store audits.Referring to FIGS. 2A and 2B, computer architecture 200 includes POSsystems 202A-202N, auditor mobile device 203, POS systems 212A-212N,auditor mobile device 213, receipt application server 221, and customermobile device 223. Each of the depicted systems, servers, and devices aswell as their respective components can be connected to one another over(or be part of) a network, such as, for example, a PAN, a LAN, a WAN,and even the Internet. Accordingly, each of the depicted components aswell as any other connected computer systems and their components, cancreate message related data and exchange message related data (e.g.,near field communication (NFC) payloads, Bluetooth packets, InternetProtocol (IP) datagrams and other higher layer protocols that utilize IPdatagrams, such as, Transmission Control Protocol (TCP), HypertextTransfer Protocol (HTTP), Simple Mail Transfer Protocol (SMTP), etc.)over the network.

POS systems 202A-202N, auditor mobile device 203, POS systems 212A-212N,auditor mobile device 213, and receipt application server 221 can becommonly owned by a merchant or retailer that operates a chain ofstores. Locations 201 and 211 can be physical store locations for themerchant or retailer. Locations 201 and 211 can be geographicallydiverse, such as, for example, in different cities, states, orcountries. The merchant or retailer can also have one or more otherphysical store locations (not depicted in FIG. 2). The ellipses before,between, and after POS systems 202A-202N and POS systems 212A-212Nrepresent that one or more additional POS systems can be included atlocation 201 and/or at location 211.

Each POS system, including POS systems 202A-202N and POS systems212A-212N can be physically located at a checkout lane in acorresponding location. Each POS system, including POS systems 202A-202Nand POS systems 212A-212N can include a transaction processor,communication modules and adapters, and I/O peripherals.

Generally, a transaction processor is configured to manage salestransactions for a POS system. The transaction processor can receiveinput from I/O peripherals to open a sales transaction, collect digitalreceipt data (e.g., date, time, item, and cost data, etc.) for the salestransaction, and close the sales transaction. An item database can storeitem data for items sold by a retailer or merchant. For example, an itemdatabase can store item description data, item cost data, item size(bulkiness) data, item profit margin data, item theft statistics, etc.for a plurality of items. Digital receipt data for an item (e.g., itemdescription and item cost) can be retrieved from the item database inresponse to scanning a barcode on (or otherwise identifying) the item.Other item data can be used internally by the merchant or retailer butnot necessarily for the generation of digital receipts.

I/O peripherals can include one or more of: a monitor (e.g., acashier-facing monitor), one or more input devices (e.g., scanners,keyboards, scales, or the like), one or more payment devices (e.g., cashdrawers, card readers, etc.) for receiving or returning payments, andone or more output devices (e.g., customer-facing display or monitor,receipt printer, etc.).

Communication modules and adapters can include wired and/or wirelessnetworking components for connecting the POS system with a network, suchas, for example, a Wi-Fi and/or wired Ethernet network, that facilitatesfurther connections (e.g., to the Internet).

Accordingly, when a sales transaction is closed, a POS system in aparticular location can use communication modules and adapters to senddigital receipt data to receipt application server 221. For example, POSsystems in location 201 can send digital receipt data to receiptapplication server 221. More particularly, POS system 202A can sendreceipt data 231, including entries 233A, 233B, etc. for items 234A,234B, etc. respectively, to receipt application server 221. Likewise,POS system 202N can send receipt data 241, including entries 243A, 243B,243C, etc. for items 244A, 244B, 244C, etc. respectively, to receiptapplication server 221.

Similarly, POS systems in location 211 can send digital receipt data toreceipt application server 221. More particularly, POS system 212A cansend receipt data 251, including entries 253A, 253B, etc. for items254A, 254B, etc. respectively, to receipt application server 221.Likewise, POS system 212N can send receipt data 261, including entries263A, 263B, etc. for items 264A, 264B, etc. respectively, to receiptapplication server 221.

Receipt database 222 can receive digital receipt data from POS systemsat various different store locations, including locations 201 and 211.Receipt database 222 can formulate digital receipts from receivedreceipt data. Formulated digital receipts can include entries for itemsincluded in corresponding digital receipt data (but potentially in adifferent format, for example, a format deliverable to mobile devices).Receipt database 222 can store formulated digital receipts in receiptdatabase 222. For example, receipt application server 221 can formulateand store digital receipts 232, 242, 252, and 262 from digital receiptdata 231, 241, 251, and 261 respectively and store digital receipts 232,242, 252, and 262 in receipt database 222.

As such, in some embodiments, receipt data server 221 is part of abackend system that receives receipt data from a plurality of POSsystems distributed throughout different geographic locations. Theplurality of POS systems and the backend system can be part of acommonly owned and/or controlled corporate network infrastructure.

Subsequent to storing digital receipts, receipt application server 221can send stored digital receipts to customer and/or auditor mobiledevices, such as, for example, smartphones and/or tablets. Receiptapplication server 221 can send digital receipts to a mobile device inresponse to a request and/or in accordance with configured settings. Forexample, in response to a request for receipts from customer mobiledevice 223, receipt application server 221 can send digital receipt 242to customer mobile device 223. Alternately or in combination, receiptapplication server 221 can send digital receipts 232 and 242 to zero ormore auditor devices, such as, for example, auditor mobile device 203,in accordance with audit settings 224. Sending digital receipts fromreceipt application server 221 to zero or more auditor devices caninvolve push or polled mechanisms. Receipt application server 221 cansend digital receipts in a web or native view. Audit settings 224 canindicate how and when to delivery digital receipts to a merchant's orretailer's store locations for use in conducting customer audits (e.g.,auditing a customer's possessed merchandise as they leave a physicalstore location).

In some embodiments, POS systems attach a location identifier to digitalreceipt data sent to receipt application server 221. Audit settings 224can include mappings between auditor mobile devices and locationidentifiers. Receipt application server 221 can use the mappings todelivery digital receipts back to an auditor mobile device at the samelocation where a sales transaction occurred.

For example, POS systems 202A-202N can attach a location identifier forlocation 201 to digital receipt data 231 and 241. Audit settings 224 caninclude a mapping between the location identifier and auditor mobiledevice 203 (an auditor mobile device for location 201). Receiptapplication server 221 can use the mapping to send corresponding digitalreceipts (i.e., digital receipts 232 and 242) back to auditor mobiledevice 203. Similarly, POS systems 212A-212N can attach a locationidentifier for location 211 to digital receipt data 251 and 261. Auditsettings 224 can include a mapping between the location identifier andauditor mobile device 213 (an auditor mobile device for location 211).Receipt application server 221 can use the mapping to send correspondingdigital receipts (i.e., digital receipts 252 and 262) back to auditormobile device 213.

As depicted, auditor mobile device 203 further includes receipt locatormodule 204, display 206, and cache 207. Auditor mobile device 213 caninclude similar or even identical components. In general, an auditormobile device can receive digital receipts from receipt applicationserver 221. The auditor mobile device can cache received digitalreceipts locally for use in conducting customer audits. For example,auditor mobile device 203 can cache digital receipts received fromreceipt application server 221 in cache 207 (e.g., system memory, aflash drive, or other storage).

An auditor mobile device can cache a digital receipt in accordance witha caching policy for a specified time period before the digital receiptis removed. The caching policy can be configured so that there is a highlikelihood of a digital receipt for a sales transaction still beingcached when a customer that participated in the sales transactionreaches a location where an audit is to occur. The caching policy canalso be configured so that a portion of cache remains available for newdigital receipts. In some embodiments, the specified time period is in arange from 5-30 minutes.

A receipt locator module at an auditor mobile device can locate digitalreceipts from within cache based on one or more identified items. Forexample, a human auditor can scan a barcode or key in information forone more items in a customer's possession. The receipt locator modulecan search the cache to locate a digital receipt that includes (matches)an entry for each of the one or more items. Matching one or moreidentified items to one or more entries of a digital receipt providessome degree of certainty that a located digital receipt corresponds tothe customer. For example, receipt locator module 204 can search cache207 to locate digital receipts that include entries for items identifiedat auditor mobile device 203.

Matched as well additional entries from a located digital receipt canthen be presented at a display device for use in conducting an in-storeaudit. A human auditor can refer to the presented entries to audit(e.g., matched and/or additional) items in the customer's possession.For example, matched and additional entries from digital receiptslocated in cache 207 can be presented at display 206. A human auditor atlocation 201 can refer to the entries presented at display 206 toperform an in-store audit of a customer. During display of digitalreceipt entries at display 206, some parts of a digital receipt can behidden from the human auditor's view to ensure customer privacy.

Prior to use of auditor mobile device 203 by a human auditor, the humanauditor can authenticate on auditor mobile device 203. The human auditorcan then select a store location, for example, based on geolocation.

FIGS. 3A and 3B illustrate a flow chart of an example method 300 forlocating digital receipt data for use in in-store audits. Method 300will be described with respect to the components and data of computerarchitecture 200.

For each of a plurality of sales transactions for a merchant, method 300includes receiving digital receipt data for a sales transactionconducted at a Point-Of-Sale (POS) system, the Point-Of-Sale (POS)system at a store location selected from among one or more storelocations, the digital receipt data containing a receipt entry for eachof one or more items purchased by a customer in the sales transaction(301). For example, receipt application server 221 can receive digitalreceipt data 231 and 241 for sales transactions conducted at POS systems202A and 202N respectively. As depicted, receipt data 231, includesentries 233A, 233B, etc. for items 234A, 234B, etc. respectivelypurchased by a customer in a sales transaction at POS system 202A.Likewise, receipt data 241 includes entries 243A, 243B, 243C, etc. foritems 244A, 244B, 244C, etc. respectively purchased by a customer in asales transaction at POS system 202N.

Similarly, receipt application server 221 can receive digital receiptdata 251 and 261 for sales transactions conducted at POS systems 212Aand 212N respectively. Receipt data 251 includes entries 253A, 253B,etc. for items 254A, 254B, etc. respectively purchased by a customer ina sales transaction at POS system 212A. Receipt data 261, includesentries 263A, 263B, etc. for items 264A, 264B, etc. respectivelypurchased by a customer in a sales transaction at POS system 212N.

Ellipsis within digital receipt data represents that entries for one ormore additional items can be included in the digital receipt data.

For each of a plurality of sales transactions for the merchant, method300 includes generating a digital receipt for the sales transaction, thedigital receipt generated from the digital receipt data, the digitalreceipt containing the receipt entry for each of the one or morepurchased items, the digital receipt providing proof of the salestransaction, the digital receipt for delivery to a customer mobiledevice associated with the customer (302). For example, receiptapplication server 221 can generate digital receipts 232, 242, 252, and262 from digital receipt data 231, 241, 251, and 261 respectively forthe sales transactions at POS systems 202A, 202N, 212A, and 212Nrespectively. Digital receipts 232, 242, 252, and 262 can be stored inreceipt database 222.

Digital receipts 232, 242, 252, and 262 provide proof of the salestransactions conducted at POS systems 202A, 202N, 212A, and 212Nrespectively. Digital receipts 232, 242, 252, and 262 can be deliveredto customer mobile devices to provide customers with a record of thesales transactions. For example, digital receipt 242 can be delivered tocustomer mobile device 223 (e.g., a mobile device associated with thecustomer that conducted the sales transaction at POS system 202N)

For each of a plurality of sales transactions for the merchant, method300 includes receiving an indication that the sales transaction is to beaudited (303). For example, receipt application server 221 can receivean indication that the sales transactions corresponding to digitalreceipts 232, 242, 252, and 262 are to be audited. In some embodiments,receipt application server is configured to audit all salestransactions. In other embodiments, receipt application server 221refers to audit settings 224 to determine if a sales transaction is tobe audited. Audit settings 224 can indicate that digital receipts withentries for specified items (e.g., higher profit margin items, bulkieritems, items that are more likely to be stolen, etc.) are to audited,can indicate that digital receipts are to be randomly audited, canindicate that digital receipts are to be audited at specified datesand/or times, can indicate that digital receipts are to be audited basedon the number of entries in a digital receipt, etc.

For each of a plurality of sales transactions for the merchant, method300 includes sending the digital receipt to an auditor mobile device atthe store location, the auditor mobile device used for in-store auditsat the store location, the digital receipt displayable at the auditormobile device such that the sales transaction can be audited withoutrequesting the digital receipt from the customer (304). For example,receipt application server 221 can send digital receipts 232 and 242 toauditor mobile device 203. Digital receipts 232 and 242 are displayableat display 206. As such, the sales transactions corresponding to digitalreceipts 232 and 242 can be audited without having to request digitalreceipt 232 or 242 from a customer.

Similarly (but not depicted), receipt application server 221 can senddigital receipts 252 and 262 to auditor mobile device 213. Digitalreceipts 252 and 262 are displayable at display of auditor mobile device213. As such, the sales transactions corresponding to digital receipts252 and 262 can be audited without having to request digital receipt 252or 262 from a customer.

Method 300 includes receiving one or more digital receipts from thereceipt application server, each of the one or more digital receipts:corresponding to a sales transaction conducted at the store location andcontaining a receipt entry for each of one or more items purchased by acustomer in the corresponding sales transaction (305). For example,auditor mobile device 203 can receive digital receipts 232 and 242 fromreceipt application server 221. As described, digital receipts 232 and242 correspond to sales transactions conducted at location 201 andcontain entries for items purchased by a customer in the correspondingsales transactions. For example, digital receipt 232 contains entries233A, 233B, etc. for items 234A, 234B, etc. respectively purchased by acustomer in the sales transaction conducted at POS system 202A.Likewise, digital receipt 242 contains entries 243A, 243B, 243C, etc.for items 244A, 244B, 244C, etc. respectively purchased by a customer inthe sales transaction conducted at POS system 202N.

Method 300 includes caching each of the one or more digital receipts atthe auditor mobile device (306). For example, auditor mobile device 203can cache digital receipts 232 and 242 in cache 207. Method 300 includesreceiving an indication that a customer is in possession of one or moreitems sold at the store location and is in an auditing area within thestore location (307). For example, receipt locator module 204 canreceive indication 271 and/or indication 272 indicating that a customeris in possession of item 244A and/or item 244C. Indications 271 and 272can be received from a peripheral device, such as, for example, abarcode scanner or keyboard, connected to auditor mobile device 203. Forexample, a human auditor can scan a barcode on an item in a customer'spossession (e.g., in a shopping cart).

Auditor mobile device 203 can be stationed at a specified audit areawithin location 211 (e.g., somewhere in a path between checkout lanesand a store exit). Thus, when an item is indicated to auditor mobiledevice 203, auditor mobile device 203 views the customer possessing theitem to be within the specified audit area.

Method 300 includes using the indication of the possessed one or moreitems to identify a digital receipt, from among the cached one or moredigital receipts, for use in an in-store audit, the digital receiptcorresponding to a sales transaction conducted at the location,identification of the digital receipt including detecting that receiptentries for the possessed one or more items are included in the digitalreceipt (308). For example, receipt locator module 204 can useindication 271 and/or indication 272 to identify digital receipt 242,from among digital receipts cached in cache 207, for use in an in-storeaudit at location 201. To identify digital receipt 242, receipt locatormodule 204 can detect that digital receipt 242 includes entry 243A foritem 244A and/or can detect that digital receipt 242 includes entry 243Cfor item 244C.

That is, one or more items identified in a customer's possession (byindications 271 and 272) are listed in a cached digital receipt (digitalreceipt 242). As such, auditor mobile device 203 has some level ofcertainty that the cached digital receipt (digital receipt 242)corresponds to the customer's sales transaction and that the cacheddigital receipt (digital receipt 242) lists other purchased items thatare to be in the customer's possession.

Method 300 includes displaying the receipt entries from the identifieddigital receipt during the in-store audit (309). For example, auditormobile device 203 can display entries 243A, 243B, 243C, etc. at display206. Entries 243A, 243B, 243C, etc. can be displayed at display 206during an in-store audit of the customer in possession of item 244Aand/or 244C. A human auditor can refer to display 206 during thein-store audit of the customer. The human auditor can check if thecustomer is in possession of any items not listed in digital receipt 242(e.g., the customer is attempting to steal an item). The human auditorcan also check if the customer lacks possession of any items listed indigital receipt 242 (e.g., the customer left an item at a checkoutlane).

During an audit or when an audit is complete, the human auditor canindicate that they are satisfied with the outcome of the audit. Forexample, the human auditor can indicate that one or more items in acustomer's possession where audited and found to be listed on thecustomer's receipt. When a human auditor is satisfied with the outcomeof an audit, the human auditor can indicate to auditor mobile device 203that a transaction was satisfactorily audited.

On the other hand, during an audit or when an audit is complete, thehuman auditor can indicate that they are not satisfied with audit. Forexample, the human auditor may find one or more items in a customer'spossession that are not listed on the customer's receipt. When a humanauditor is not satisfied with an audit, the human auditor can indicateto auditor mobile device 203 that there is a problem with the auditor.Alternately, the human auditor can call other employees to assist. Forexample, an unsatisfactory audit can be escalated to more senior stafffor performance of other measures, such as, for example, reviewingsecurity footage.

Auditor mobile device 213 can repeat 305-309 to identify and displayappropriate digital receipts for use in in-store audits at location 211.

FIGS. 4A and 4B illustrates an example computer architecture 400 thatfacilitates locating and reordering digital receipt data for use in anin-store audit. Referring to FIGS. 4A and 4B, computer architecture 400includes POS systems 402A-402N, auditor mobile device 403, receiptapplication server 421, and customer mobile device 423. Each of thedepicted systems, servers, and devices as well as their respectivecomponents can be connected to one another over (or be part of) anetwork, such as, for example, a PAN, a LAN, a WAN, and even theInternet. Accordingly, each of the depicted components as well as anyother connected computer systems and their components, can createmessage related data and exchange message related data (e.g., near fieldcommunication (NFC) payloads, Bluetooth packets, Internet Protocol (IP)datagrams and other higher layer protocols that utilize IP datagrams,such as, Transmission Control Protocol (TCP), Hypertext TransferProtocol (HTTP), Simple Mail Transfer Protocol (SMTP), etc.) over thenetwork.

POS systems 402A-402N, auditor mobile device 403, and receiptapplication server 421 can be commonly owned by a merchant or retailerthat operates a chain of stores. Location 401 can be a physical storelocation for the merchant or retailer. The merchant or retailer can alsohave one or more other physical store locations (not depicted in FIG.4). Location 401 and any other locations can be geographically diverselocations, such as, for example, in different cities, states, orcountries. The ellipses before, between, and after POS systems 402A-402Nrepresent that one or more additional POS systems can be included atlocation 401.

Each POS system, including POS systems 402A-402N can be physicallylocated at a checkout lane. Each POS system, including POS systems402A-402N can include a transaction processor, communication modules andadapters, and I/O peripherals.

Generally, a transaction processor is configured to manage salestransactions for a POS system. The transaction processor can receiveinput from I/O peripherals to open a sales transaction, collect digitalreceipt data (e.g., date, time, item, and cost data, etc.) for the salestransaction, and close the sales transaction. An item database can storeitem data for items sold by a retailer or merchant. For example, an itemdatabase can store item description data, item cost data, item size(bulkiness) data, item profit margin data, item theft statistics (howlikely is the item to be stolen), etc. for a plurality of items. Digitalreceipt data for an item (e.g., item description and item cost) can beretrieved from the item database in response to scanning a barcode on(or otherwise identifying) the item. Other item data can be usedinternally by the merchant or retailer but not necessarily for thegeneration of digital receipts.

I/O peripherals can include one or more of: a monitor (e.g., acashier-facing monitor), one or more input devices (e.g., scanners,keyboards, scales, or the like), one or more payment devices (e.g., cashdrawers, card readers, etc.) for receiving or returning payments, andone or more output devices (e.g., customer-facing display or monitor,receipt printer, etc.).

Communication modules and adapters can include wired and/or wirelessnetworking components for connecting the POS system with a network, suchas, for example, a Wi-Fi and/or wired Ethernet network, that facilitatesfurther connections (e.g., to the Internet).

Accordingly, when a sales transaction is closed, a POS system in aparticular location can use communication modules and adapters to senddigital receipt data to receipt application server 421. For example, POSsystems in location 401 can send digital receipt data to receiptapplication server 421. More particularly, POS system 402A can sendreceipt data 431, including entries 433A, 433B, 433C etc. for items434A, 434B, 4334C, etc. respectively, to receipt application server 421.Likewise, POS system 402N can send receipt data 441, including entries443A, 443B, etc. for items 444A, 444B, etc. respectively, to receiptapplication server 421.

Receipt database 422 can receive digital receipt data from POS systemsat various different store locations, including location 401. Receiptdatabase 422 can formulate digital receipts from received receipt data.Formulated digital receipts can include entries for items included incorresponding digital receipt data (but potentially in a differentformat, for example, a format deliverable to mobile devices). Receiptdatabase 422 can store formulated digital receipts in receipt database422. For example, receipt application server 421 can formulate and storedigital receipts 432 and 442 from digital receipt data 431 and 441respectively. Receipt application server 421 can also formulate otherdigital receipts 428 for other receipt data 427 (e.g., digital receiptdata from other store locations). Receipt application server 421 canstore digital receipts 432, 434, and other receipts 428 in receiptdatabase 422.

As such, in some embodiments, receipt data server 421 is part of abackend system that receives receipt data from a plurality of POSsystems distributed throughout different geographic locations. Theplurality of POS systems and the backend system can be part of acommonly owned and/or controlled corporate network infrastructure.

Subsequent to storing digital receipts, receipt application server 421can send stored digital receipts to customer and/or auditor mobiledevices, such as, for example, smartphones and/or tablets. Receiptapplication server 421 can send digital receipts to a mobile device inresponse to a request and/or in accordance with configured settings. Forexample, in response to a request for receipts from customer mobiledevice 423, receipt application server 421 can send digital receipt 432to customer mobile device 423. Alternately or in combination, receiptapplication server 421 can send digital receipts 432 and 442 to zero ormore auditor devices, such as, for example, auditor mobile device 403,in accordance with audit settings 424. Sending digital receipts fromreceipt application server 421 to zero or more auditor devices caninvolve push or polled mechanisms. Receipt application server 421 cansend digital receipts in a web or native view. Audit settings 424 canindicate how and when to delivery digital receipts to a merchant's orretailer's store locations for use in conducting customer audits (e.g.,auditing a customer's possessed merchandise as they leave a physicalstore location).

In some embodiments, POS systems attach a location identifier to digitalreceipt data sent to receipt application server 421. Audit settings 424can include mappings between auditor mobile devices and locationidentifiers. Receipt application server 421 can use the mappings todelivery digital receipts back to an auditor mobile device at the samelocation where a sales transaction occurred.

For example, POS systems 402A and 402N can attach a location identifierfor location 401 to digital receipt data 431 and 441 respectively. Auditsettings 424 can include a mapping between the location identifier andauditor mobile device 403 (an auditor mobile device for location 401).Receipt application server 421 can use the mapping to send correspondingdigital receipts (i.e., digital receipts 432 and 442) back to auditormobile device 403. Audit settings 224 can also include mappings betweenlocation identifiers and auditor mobile devices in other locations(e.g., store locations that sent other digital receipt data 427).Receipt application server 421 can use the mappings to sendcorresponding digital receipts back to other auditor mobile devices.

As depicted, auditor mobile device 403 further includes receipt locatormodule 404, display 406, cache 407, and reordering module 408. Ingeneral, an auditor mobile device can receive digital receipts fromreceipt application server 421. The auditor mobile device can cachereceived digital receipts locally for use in conducting customer audits.For example, auditor mobile device 403 can cache digital receiptsreceived from receipt application server 421 in cache 407 (e.g., systemmemory, a flash drive, or other storage).

An auditor mobile device can cache a digital receipt in accordance witha caching policy for a specified time period before the digital receiptis removed. The caching policy can be configured so that there is a highlikelihood of a digital receipt for a sales transaction still beingcached when a customer that participated in the sales transactionreaches a location where an audit is to occur. The caching policy canalso be configured so that a portion of cache remains available for newdigital receipts. In some embodiments, the specified time period is in arange from 5-30 minutes.

A receipt locator module at an auditor mobile device can locate digitalreceipts from within cache based on one or more identified items. Forexample, a human auditor can scan a barcode or key in information forone more items in a customer's possession. The receipt locator modulecan search the cache to locate a digital receipt that includes (matches)an entry for each of the one or more items. Matching one or moreidentified items to one or more entries of a digital receipt providessome degree of certainty that a located digital receipt corresponds tothe customer. For example, receipt locator module 404 can search cache407 to locate digital receipts that include entries for items identifiedat auditor mobile device 403.

A reordering module can refer to audit rules to determine how matched aswell as additional entries from located digital receipts are to beordered for presentation at a display device. For example, reorderingmodule 408 can refer to audit rules 426 to determine how entries fromlocated receipts are to be ordered for presentation at display 406.Audit rules can indicate how to reorder entries of a digital receipt fordisplay based on items characteristics. For example, audit rules canindicate that items with higher profit margins, larger (or bulkier)items, items that are more likely to be stolen, etc. are to be presentedmore prominently at a display.

Reordered entries from a located digital receipt can then be presentedat a display device for use in conducting an in-store audit. A humanauditor can refer to the presented entries to audit (e.g., matchedand/or additional) items in the customer's possession. For example,reordered entries from digital receipts located in cache 407 can bepresented at display 406. A human auditor at location 401 can refer tothe entries presented at display 406 to perform an in-store audit of acustomer. During display of digital receipt entries at display 406, someparts of a digital receipt can be hidden from the human auditor's viewto ensure customer privacy.

The human auditor may also chose to apply different audit prioritiesafter viewing reordered receipt entries. For example, if receipt entrieswhere initially ordered by profit margin, the human auditor may chooseto reorder based on bulk or likelihood of theft.

Prior to use of auditor mobile device 403 by a human auditor, the humanauditor can authenticate on auditor mobile device 403. The human auditorcan then select a store location, for example, based on geolocation.

FIGS. 5A and 5B illustrate a flow chart of an example method 500 forlocating and reordering digital receipt data for use in an in-storeaudit. Method 500 will be described with respect to the components anddata of computer architecture 400.

Method 500 includes receiving digital receipt data for a salestransaction conducted at a Point-Of-Sale (POS) system, the Point-Of-Sale(POS) system in a store location selected from among the one or morestore locations, the digital receipt data containing a receipt entry foreach of one or more items purchased by a customer in the salestransaction (501). For example, receipt application server 421 canreceive digital receipt data 431 for a sales transaction conducted atPOS system 402A. Digital receipt data 431 contains entries 433A, 433B,434C, etc. for items 434A, 434B, 434C, etc. purchased in the salestransaction by a customer at location 401.

Method 500 includes generating a digital receipt for the salestransaction, the digital receipt generated from the digital receiptdata, the digital receipt containing the receipt entry for each of theone or more purchased items, the digital receipt providing proof of thesales transaction, the digital receipt for delivery to a customer mobiledevice associated with the customer (502). For example, receiptapplication server 421 can generate digital receipt 432 from digitalreceipt data 431. Digital receipt 432 provides proof of the salestransaction at POS system 402A. Digital receipt 432 can be delivered toa customer mobile device associated with the customer.

Method 500 includes receiving an indication that the sales transactionis to be audited in the store location (503). For example, receiptapplication server 421 can receive an indication that the salestransactions corresponding to digital receipt 432 is to be audited. Insome embodiments, receipt application server 421 is configured to auditall sales transactions. In other embodiments, receipt application server421 refers to audit settings 424 to determine if a sales transaction isto be audited. Audit settings 424 can indicate that digital receiptswith entries for specified items (e.g., higher profit margin items,bulkier items, items that are more likely to be stolen, etc.) are toaudited, can indicate that digital receipts are to be randomly audited,can indicate that digital receipts are to be audited at specified datesand/or times, can indicate that digital receipts are to be audited basedon the number of entries in a digital receipt, etc.

Method 500 includes sending the digital receipt to an auditor mobiledevice at the store location, the auditor mobile device used to reorderreceipt entries in accordance with audit rules, the audit rules definingan audit priority for each of the one or more purchased items based oncharacteristics of each of the one or more purchased items, an auditpriority for an item indicating an importance of expressly validatingthe item during the in-store audit, the reordered entries displayableduring in-store audits to increase the likelihood of expresslyvalidating items with higher indicated importance during the in-storeaudit (504). For example, receipt application server 421 can senddigital receipt 432 to auditor mobile device 403. Prior to or aftersending digital receipt 432, receipt application server 421 can alsosend digital receipt 442 (as well as other digital receipts for salestransactions conducted at location 401) to auditor mobile device 403.

Method 500 includes receiving a digital receipt from the receiptapplication server, the digital receipt corresponding to the salestransaction conducted at the store location, the digital receiptcontaining a receipt entry for each of one or more items purchased by acustomer in the sales transaction (505). For example, auditor mobiledevice 403 can receive digital receipt 432 from receipt applicationserver 421. Prior to or after receiving digital receipt 432, auditormobile device 403 can also receive digital receipt 442 (as well as otherdigital receipts for sales transactions conducted at location 401) fromreceipt application server 421.

Method 500 includes caching the digital receipt at the auditor mobiledevice (506). For example, auditor mobile device 403 can cache digitalreceipt 432 in cache 407. Prior to or after caching digital receipt 432,auditor mobile device 403 can also cache digital receipt 442 (as well asother digital receipts for sales transactions conducted at location 401)in cache 407.

Method 500 includes subsequent to caching the digital receipt, receivingan indication that a customer is in possession of one or more items soldat the store location and is in an auditing area within the storelocation (507). For example, receipt locator module 404 can receiveindication 471 and/or indication 472 indicating that a customer is inpossession of item 444B and/or item 444C. Indications 471 and 472 can bereceived from a peripheral device, such as, for example, a barcodescanner or keyboard, connected to auditor mobile device 403. Forexample, a human auditor can scan a barcode on an item in a customer'spossession (e.g., in a shopping cart).

Auditor mobile device 403 can be stationed at a specified audit areawithin location 401 (e.g., somewhere in a path between checkout lanesand a store exit). Thus, when an item is indicated to auditor mobiledevice 403, auditor mobile device 403 views the customer possessing theitem to be within the specified audit area.

Method 500 includes using the indication of the possessed one or moreitems to identify the digital receipt, from among one or more digitalreceipts cached at the auditor mobile device, for use in an in-storeaudit, identification of the digital receipt including detecting thatreceipt entries for the possessed one or more items are included in thedigital receipt (508). For example, receipt locator module 404 can useindication 471 and/or indication 472 to identify digital receipt 432,from among digital receipts cached in cache 407, for use in an in-storeaudit at location 401. To identify digital receipt 432, receipt locatormodule 404 can detect that digital receipt 432 includes entry 433B foritem 434B and/or can detect that digital receipt 432 includes entry 433Cfor item 434C.

That is, one or more items identified in a customer's possession (byindications 471 and 472) are listed in a cached digital receipt (digitalreceipt 432). As such, auditor mobile device 403 has some level ofcertainty that the cached digital receipt (digital receipt 432)corresponds to the customer's sales transaction and that the cacheddigital receipt (digital receipt 432) lists other purchased items thatare to be in the customer's possession.

Method 500 includes referring to audit rules, the audit rules definingan audit priority for each of the one or more purchased items based oncharacteristics of each of the one or more purchased items, an auditpriority for an item indicating an importance of expressly validatingthe item during the in-store audit (509). For example, reordering module408 can refer to audit rules 426. Audit rules 426 represent a merchantor retailer defined audit priority for each of items 434A, 434B, 434C,etc. based on characteristics of each of items 434A, 434B, 434C, etc.For example, audit rules 426 can indicate that the merchant or retailerhas placed increased importance on expressly validating items withspecified characteristics, such as, for example, higher profit marginsitems, bulkier items, items that are more likely to be stolen, etc.during an in-store audit.

Method 500 includes reordering the receipt entries of the identifieddigital receipt in accordance with the defined audit priority for eachof the one or more items (510). For example, reordering module 408 canreorder entries 433A, 433B, 433C, etc. of digital receipt 432 inaccordance with the defined audit priority for each of items 434A, 434B,434C, etc. Items 434A, 434B, 434C, etc. can be reordered to increase thelikelihood of items with higher indicated importance being expresslyvalidated during the in-store audit. Reordering receipt entries caninclude changing the original ordering of entries in a digital receipt.An original (or default) ordering can be the order in which items wherescanned at the time of the sales transactions (e.g., the salestransaction for which digital receipt 432 was generated).

For example, it may be that a merchant or retailer has defined auditrules 426 to indicate that items are to be ordered by highest profitmargin. If item 434C is the highest profit margin item on digitalreceipt 432, reordering module 408 can order entry 433C for display withincreased prominence. If item 434A is the second highest profit marginitem on digital receipt 432, reordering module 408 can order entry 433Afor display with increased prominence but somewhat less prominence thanentry 433C. Reordering module 408 can order other entries on digitalreceipt 432 for display prominence concomitant with corresponding itemprofit margins. For example, reordering module 408 can order entry 433Bfor somewhat lower display prominence relative to entries 433C and 433Abut with higher display prominence than some other receipt entries.

In other embodiments, reordering module 408 can reorder digital receiptentries by item bulkiness, likelihood of items being stolen, etc.Reordering module 408 can refer to an item database (e.g., the itemdatabase used by POS systems at location 401) to access itemcharacteristics for items listed on a digital receipt.

Method 500 includes displaying the reordered receipt entries during thein-store audit so as to increase the likelihood of items with higherindicated importance being expressly validated during the in-store audit(511). For example, auditor mobile device 403 can display reorderedentries from digital receipt 432 at display 406. The reordered entriescan be displayed in a list format with the first ordered entry at thetop and followed by other entries in descending order. For example,entry 433C can be displayed at the top of the list at display 406. Entry433A can be displayed directly below entry 433C on the list at display406. Entry 433B can be displayed one or more entries below entry 433A onthe list at display 406. One or more other entries can be displayedbelow entry 433B on the list at display 406.

Reordered entries from digital receipt can be displayed at display 406during an in-store audit of the customer in possession of item 434Band/or item 434C. A human auditor can refer to display 406 during thein-store audit of the customer. The human auditor can check if thecustomer is in possession of any items not listed in digital receipt 432(e.g., the customer is attempting to steal an item). The human auditorcan also check if the customer lacks possession of any items listed indigital receipt 432 (e.g., the customer left an item at a checkoutlane). Since receipt entries for higher importance items are displayednearer to the top of display 406, there is increased likelihood that thehuman auditor expressly validates these higher importance items sincethey can be more efficiently viewed.

In other embodiments, the prominence of displayed digital receiptentries can be increased or decreased by varying font size, varying fontcolor, varying location on display 406, etc.

During an audit or when an audit is complete, the human auditor canindicate that they are satisfied with the outcome of the audit. Forexample, the human auditor can indicate that one or more items in acustomer's possession where audited and found to be listed on thecustomer's receipt. When a human auditor is satisfied with the outcomeof an audit, the human auditor can indicate to auditor mobile device 403that a transaction was satisfactorily audited.

On the other hand, during an audit or when an audit is complete, thehuman auditor can indicate that they are not satisfied with audit. Forexample, the human auditor may find one or more items in a customer'spossession that are not listed on the customer's receipt. When a humanauditor is not satisfied with an audit, the human auditor can indicateto auditor mobile device 403 that there is a problem with the auditor.Alternately, the human auditor can call other employees to assist. Anunsatisfactory audit can be escalated to more senior staff forperformance of other measures, such as, for example, reviewing securityfootage.

FIGS. 6A and 6B illustrates an example computer architecture 600 thatfacilitates locating and reordering digital receipt data for use in anin-store audit. Referring to FIGS. 6A and 6B, computer architecture 600includes POS systems 602A-602C, auditor mobile device 603, receiptapplication server 621, and customer mobile device 623. Each of thedepicted systems, servers, and devices as well as their respectivecomponents can be connected to one another over (or be part of) anetwork, such as, for example, a PAN, a LAN, a WAN, and even theInternet. Accordingly, each of the depicted components as well as anyother connected computer systems and their components, can createmessage related data and exchange message related data (e.g., near fieldcommunication (NFC) payloads, Bluetooth packets, Internet Protocol (IP)datagrams and other higher layer protocols that utilize IP datagrams,such as, Transmission Control Protocol (TCP), Hypertext TransferProtocol (HTTP), Simple Mail Transfer Protocol (SMTP), etc.) over thenetwork.

POS systems 602A-602C, auditor mobile device 603, and receiptapplication server 621 can be commonly owned by a merchant or retailerthat operates a chain of stores. Location 601 can be a physical storelocation for the merchant or retailer. The merchant or retailer can alsohave one or more other physical store locations (not depicted in FIG.6). Location 601 and any other locations can be geographically diverselocations, such as, for example, in different cities, states, orcountries. The ellipses before, between, and after POS systems 602A-602Crepresent that one or more additional POS systems can be included atlocation 601.

Each POS system, including POS systems 602A-602C can be physicallylocated at a checkout lane. Each POS system, including POS systems602A-602C can include a transaction processor, communication modules andadapters, and I/O peripherals.

Generally, a transaction processor is configured to manage salestransactions for a POS system. The transaction processor can receiveinput from I/O peripherals to open a sales transaction, collect digitalreceipt data (e.g., date, time, item, and cost data, etc.) for the salestransaction, and close the sales transaction. An item database can storeitem data for items sold by a retailer or merchant. For example, an itemdatabase can store item description data, item cost data, item size(bulkiness) data, item profit margin data, item theft statistics (howlikely is the item to be stolen), etc. for a plurality of items. Digitalreceipt data for an item (e.g., item description and item cost) can beretrieved from the item database in response to scanning a barcode on(or otherwise identifying) the item. Other item data can be usedinternally by the merchant or retailer but not necessarily for thegeneration of digital receipts.

I/O peripherals can include one or more of: a monitor (e.g., acashier-facing monitor), one or more input devices (e.g., scanners,keyboards, scales, or the like), one or more payment devices (e.g., cashdrawers, card readers, etc.) for receiving or returning payments, andone or more output devices (e.g., customer-facing display or monitor,receipt printer, etc.).

Communication modules and adapters can include wired and/or wirelessnetworking components for connecting the POS system with a network, suchas, for example, a Wi-Fi and/or wired Ethernet network, that facilitatesfurther connections (e.g., to the Internet).

Accordingly, when a sales transaction is closed, a POS system in aparticular location can use communication modules and adapters to senddigital receipt data to receipt application server 621. For example, POSsystems in location 601 can send digital receipt data to receiptapplication server 621. More particularly, POS system 602C can sendreceipt data 631, including entries 633A, 633B, 633C, 633D, etc. foritems 634A, 634B, 6334C, 634D, etc. respectively, to receipt applicationserver 621. Likewise, other POS systems at location 601 (e.g., POSsystem 602A) can send receipt data to receipt application server 621.

Receipt database 622 can receive digital receipt data from POS systemsat various different store locations, including location 601. Receiptdatabase 622 can formulate digital receipts from received receipt data.Formulated digital receipts can include entries for items included incorresponding digital receipt data (but potentially in a differentformat, for example, a format deliverable to mobile devices). Receiptdatabase 622 can store formulated digital receipts in receipt database622. For example, receipt application server 621 can formulate and storedigital receipts 632 from digital receipt data 631. Receipt applicationserver 621 can also formulate other digital receipts 628 for otherreceipt data 627 (e.g., digital receipt data from other storelocations). Receipt application server 621 can store digital receipts632 and other receipts 628 in receipt database 622.

As such, in some embodiments, receipt data server 621 is part of abackend system that receives receipt data from a plurality of POSsystems distributed throughout different geographic locations. Theplurality of POS systems and the backend system can be part of acommonly owned and/or controlled corporate network infrastructure.

Subsequent to storing digital receipts, receipt application server 621can send stored digital receipts to customer and/or auditor mobiledevices, such as, for example, smartphones and/or tablets. Receiptapplication server 621 can send digital receipts to a mobile device inresponse to a request and/or in accordance with configured settings. Forexample, in response to a request for receipts from customer mobiledevice 623, receipt application server 621 can send digital receipt 632to customer mobile device 623. Alternately or in combination, receiptapplication server 621 can send digital receipts 632 and other digitalreceipts 629 (e.g., a subset of other digital receipts 628) to zero ormore auditor devices, such as, for example, auditor mobile device 603,in accordance with audit settings 624. Sending digital receipts fromreceipt application server 621 to zero or more auditor devices caninvolve push or polled mechanisms. Receipt application server 621 cansend digital receipts in a web or native view. Audit settings 624 canindicate how and when to delivery digital receipts to a merchant's orretailer's store locations for use in conducting customer audits (e.g.,auditing a customer's possessed merchandise as they leave a physicalstore location).

In some embodiments, POS systems attach a location identifier to digitalreceipt data sent to receipt application server 621. Audit settings 624can include mappings between auditor mobile devices and locationidentifiers. Receipt application server 621 can use the mappings todelivery digital receipts back to an auditor mobile device at the samelocation where a sales transaction occurred.

For example, POS system 602C can attach a location identifier forlocation 601 to digital receipt data 631. Audit settings 624 can includea mapping between the location identifier and auditor mobile device 603(an auditor mobile device for location 601). Receipt application server621 can use the mapping to send corresponding digital receipts (e.g.,digital receipt 632) back to auditor mobile device 603. Audit settings624 can also include mappings between location identifiers and auditormobile devices in other locations (e.g., store locations that sent otherdigital receipt data 627). Receipt application server 621 can use themappings to send corresponding digital receipts back to other auditormobile devices.

Receipt application server 621 also includes ordering data generationmodule 618. Ordering data generation module 618 is configured togenerate receipt entry ordering data. Receipt entry ordering datainstructs an auditor mobile device how to order receipt entries forpresentation at a display. Ordering data generation module 618 can referto audit rules to determine how receipt entries are to be ordered forpresentation at the display device. For example, ordering datageneration module 618 can refer to audit rules 626 to determine howreceipts entries are to be ordered for presentation at display 606.Audit rules can indicate how to reorder entries of a digital receipt fordisplay based on item characteristics. For example, audit rules canindicate that items with higher profit margins, larger (or bulkier)items, items that are more likely to be stolen, etc. are to be presentedmore prominently at a display.

In some embodiments, generated receipt entry ordering data includesinstructions expressly instructing an auditor mobile device how to orderreceipt entries. For example, ordering data generation module 618 canprocess audit rules 626 to generate a set of instructions that can beexecuted by a reordering module at an auditor mobile device. In theseembodiments, reordering modules can include less advanced decisionmaking and processing capabilities.

In other embodiments, receipt entry ordering data includes an applicablesubset of audit rules 626. For example, ordering data generation module618 can extract an applicable portion of audit rules 626 for processingby reordering module at an auditor mobile device. Receipt entry orderingdata can be sent along with or separately from a digital receipt. Inthese other embodiments, reordering modules can include more advanceddecision making and processing capabilities.

Receipt entry ordering data can be generated and sent to an auditormobile device on a per digital receipt basis. Alternately, receipt entryordering data can be generated and sent to an auditor mobile device lessfrequently.

As depicted, auditor mobile device 603 further includes receipt locatormodule 604, display 606, cache 607, and reordering module 608. Ingeneral, an auditor mobile device can receive digital receipts andreceipt entry ordering data from receipt application server 621. Theauditor mobile device can cache received digital receipts (possiblyalong with corresponding receipt entry ordering data) locally for use inconducting customer audits. For example, auditor mobile device 603 cancache digital receipts and corresponding receipt entry ordering datareceived from receipt application server 621 in cache 607 (e.g., systemmemory, a flash drive, or other storage).

When receipt entry ordering data is generated and sent per digitalreceipt, an auditor mobile device can cache a digital receipt andcorresponding receipt entry ordering data in accordance with a cachingpolicy for a specified time period before the digital receipt andreceipt entry ordering data are removed. The caching policy can beconfigured so that there is a high likelihood of a digital receipt andcorresponding receipt entry ordering data for a sales transaction stillbeing cached when a customer that participated in the sales transactionreaches a location where an audit is to occur. The caching policy canalso be configured so that a portion of cache remains available for newdigital receipts and receipt entry ordering data. In some embodiments,the specified time period is in a range from 5-30 minutes.

When receipt entry ordering data is generated and sent less frequently(and is thus applicable to a plurality of different digital receipts),the receipt entry ordering data may or may not be cached at cache 607.For example, in some embodiments, receipt entry ordering data bypassescache 607 and is maintained at reordering module 608.

A receipt locator module at an auditor mobile device can locate digitalreceipts and, when appropriate, corresponding receipt entry orderingdata, from within cache based on one or more identified items. Forexample, a human auditor can scan a barcode or key in information forone more items in a customer's possession. The receipt locator modulecan search the cache to locate a digital receipt that includes (matches)an entry for each of the one or more items. Matching one or moreidentified items to one or more entries of a digital receipt providessome degree of certainty that a located digital receipt (and receiptentry ordering data) corresponds to the customer. For example, receiptlocator module 604 can search cache 607 to locate digital receipts thatinclude (and receipt entry ordering data for) entries for itemsidentified at auditor mobile device 603.

A reordering module can refer to receipt entry ordering data todetermine how matched as well as additional entries from located digitalreceipts are to be ordered for presentation at a display device. Forexample, reordering module 608 can refer to receipt entry ordering data624 to determine how entries from located receipts are to be ordered forpresentation at display 606. Receipt entry ordering data can indicatehow to reorder entries of a digital receipt for display based on itemscharacteristics. For example, receipt entry ordering data can indicatethat items with higher profit margins, larger (or bulkier) items, itemsthat are more likely to be stolen, etc. are to be presented moreprominently at a display.

When receipt entry ordering data includes express instructions, areordering module can execute the instructions to reorder receiptentries. On the other hand, when receipt entry ordering data includes asubset of audit rules 626, a reordering module can process the auditrules to determine how to reorder receipt entries.

Reordered entries from a located digital receipt can then be presentedat a display device for use in conducting an in-store audit. A humanauditor can refer to the presented entries to audit (e.g., matchedand/or additional) items in the customer's possession. For example,reordered entries from digital receipts located in cache 607 can bepresented at display 606. A human auditor at location 601 can refer tothe entries presented at display 606 to perform an in-store audit of acustomer. During display of digital receipt entries at display 606, someparts of a digital receipt can be hidden from the human auditor's viewto ensure customer privacy.

The human auditor may also chose to apply different audit prioritiesafter viewing reordered receipt entries. For example, if receipt entrieswhere initially ordered by bulk the human auditor may choose to reorderbased on profit margin or likelihood of theft.

Prior to use of auditor mobile device 603 by a human auditor, the humanauditor can authenticate on auditor mobile device 603. The human auditorcan then select a store location, for example, based on geolocation.

FIGS. 7A and 7B illustrates a flow chart of an example method 700 forlocating and reordering digital receipt data for use in an in-storeaudit. Method 700 will be described with respect to the components anddata of computer architecture 600.

Method 700 includes receiving digital receipt data for a salestransaction conducted at a Point-Of-Sale (POS) system, the Point-Of-Sale(POS) system in a store location selected from among the one or morestore locations, the digital receipt data containing a receipt entry foreach of one or more items purchased by a customer in the salestransaction (701). For example, receipt application server 621 canreceive digital receipt data 631 for a sales transaction conducted atPOS system 602C. Digital receipt data 631 contains entries 633A, 633B,633C, 633D, etc. for items 634A, 634B, 634C, 634D, etc. purchased in thesales transaction by a customer at location 601.

Method 700 includes generating a digital receipt for the salestransaction, the digital receipt generated from the digital receiptdata, the digital receipt containing the receipt entry for each of theone or more purchased items, the digital receipt providing proof of thesales transaction, the digital receipt for delivery to a customer mobiledevice associated with the customer (702). For example, receiptapplication server 621 can generate digital receipt 632 from digitalreceipt data 631. Digital receipt 632 provides proof of the salestransaction at POS system 602C. Digital receipt 632 can be delivered toa customer mobile device associated with the customer.

Method includes receiving an indication that the sales transaction is tobe audited in the store location (703). For example, receipt applicationserver 621 can receive an indication that the sales transactionscorresponding to digital receipt 632 is to be audited. In someembodiments, receipt application server 621 is configured to audit allsales transactions. In other embodiments, receipt application server 621refers to audit settings 624 to determine if a sales transaction is tobe audited. Audit settings 624 can indicate that digital receipts withentries for specified items (e.g., higher profit margin items, bulkieritems, items that are more likely to be stolen, etc.) are to audited,can indicate that digital receipts are to be randomly audited, canindicate that digital receipts are to be audited at specified datesand/or times, can indicate that digital receipts are to be audited basedon the number of entries in a digital receipt, etc.

Method 700 includes accessing receipt entry ordering data, the receiptentry ordering data specifying how receipt entries are to be ordered toincrease the likelihood of items with specified characteristics beingexpressly validated during an in-store audit (704). For example,ordering data generation module 618 can generate receipt entry orderingdata 624. Receipt entry ordering data 624 specifies how receipt entriesare to be ordered to increase the likelihood of items with specifiedcharacteristics being expressly validated during an in-store audit atlocation 601. Receipt entry ordering data 624 can include a subset ofaudit rules 626 or can include express instructions generated fromdefinitions included in audit rules 626.

Audit rules 626 represent merchant or retailer defined audit prioritiesfor items based on the characteristics of the items. For example, auditrules 626 can indicate that the merchant or retailer has placedincreased importance on expressly validating items with specifiedcharacteristics, such as, for example, higher profit margins items,bulkier items, items that are more likely to be stolen, etc. during anin-store audit.

Method 700 includes sending the digital receipt and receipt entryordering data to an auditor mobile device at the store location, theauditor mobile device used for in-store audits at the store location,the receipt entries displayable at the auditor mobile device inaccordance with the receipt entry ordering data such that the likelihoodof expressly validating items having the specified characteristics isincreased during the in-store audit of the sales transaction (705). Forexample, receipt application server 621 can send digital receipt 632 andreceipt entry ordering data 624 to auditor mobile device 603. Receiptapplication server 621 can send digital receipt 632 along with orseparate from receipt entry ordering data 624. Prior to or after sendingdigital receipt 632, receipt application server 621 can also send otherdigital receipts 629 (as well as other receipt entry ordering data asappropriate) to auditor mobile device 603.

Method 700 includes receiving a digital receipt and receipt entryordering data from the receipt application server, the digital receiptcorresponding to a sales transaction conducted at the store location,the digital receipt containing a receipt entry for each of one or moreitems purchased by a customer in the sales transaction, the receiptentry ordering data specifying how receipt entries are to be ordered toincrease the likelihood of items with specified characteristics beingexpressly validated during an in-store audit (706). For example, auditormobile device 603 can receive digital receipt 632 and receipt entryordering data 624 from receipt application server 621. Auditor mobiledevice 603 can receive digital receipt 632 along with or separate fromreceipt entry ordering data 624. Prior to or after receiving digitalreceipt 632, auditor mobile device 603 can also receive other digitalreceipts 629 (as well as other receipt entry ordering data asappropriate) from receipt application server 621.

Method 700 includes caching the digital receipt at the auditor mobiledevice (707). For example, auditor mobile device 603 can cache digitalreceipt 632 in cache 607. Prior to or after caching digital receipt 632,auditor mobile device 603 can also cache other digital receipts 629. Insome embodiments, auditor mobile device 603 caches receipt entryordering data 624 (as well as other receipt entry ordering data receivedfrom receipt application server 621). In other embodiments, auditormobile device 603 sends receipt entry ordering data 624 (as well asother receipt entry ordering data received from receipt applicationserver 621) to reordering module 608.

Method 700 includes subsequent to caching the digital receipt, receivingan indication that a customer is in possession of one or more items soldat the store location and is in an auditing area within the storelocation (708). For example, receipt locator module 604 can receive oneor more of indications 671, 672, and 673 indicating that a customer isin possession of items 634A, 634C, and 634D. Indications 671, 672, and673 can be received from a peripheral device, such as, for example, abarcode scanner or keyboard, connected to auditor mobile device 603. Forexample, a human auditor can scan a barcode on an item in a customer'spossession (e.g., in a shopping cart).

Auditor mobile device 603 can be stationed at a specified audit areawithin location 601 (e.g., somewhere in a path between checkout lanesand a store exit). Thus, when an item is indicated to auditor mobiledevice 603, auditor mobile device 603 views the customer possessing theitem to be within the specified audit area.

Method 700 includes using the indication of the possessed one or moreitems to identify the digital receipt, from among one or more digitalreceipts cached at the auditor mobile device, for use in an in-storeaudit, identification of the digital receipt including detecting thatreceipt entries for the possessed one or more items are included in thedigital receipt (709). For example, receipt locator module 604 can useone or more of: indications 671, 672, and 673 to identify digitalreceipt 632, from among digital receipts cached in cache 607, for use inan in-store audit at location 601. To identify digital receipt 632,receipt locator module 604 can detect that digital receipt 632 includesone or more of: entry 633A for item 634A, entry 633C for item 634C, andentry 633D for item 634D.

That is, one or more items identified in a customer's possession (byindications 671, 672, and 673) are listed in a cached digital receipt(digital receipt 632). As such, auditor mobile device 603 has some levelof certainty that the cached digital receipt (digital receipt 632)corresponds to the customer's sales transaction and that the cacheddigital receipt (digital receipt 632) lists other purchased items thatare to be in the customer's possession.

Method 700 includes reordering the receipt entries of the digitalreceipt in accordance with the receipt entry ordering data (710). Forexample, reordering module 608 can reorder entries 633A, 633B, 633C,633D etc., of digital receipt 632 in accordance with receipt entryordering data 624. Entries 633A, 633B, 633C, 633D, etc, can be reorderedto increase the likelihood of items with higher indicated importancebeing expressly validated during the in-store audit. Reordering receiptentries can include changing the original ordering of entries in adigital receipt. An original (or default) ordering can be the order inwhich items where scanned at the time of the sales transactions (e.g.,the sales transaction for which digital receipt 632 was generated).

When appropriate, reordering module 608 can access receipt entryordering data 624 from cache 607.

In some embodiments, reordering module 608 executes express instructionsincluded in receipt entry ordering data 624 to reorder receipt entriesof digital receipt 632. In other embodiments, reordering module 608refers to defined audit priorities (in a subset of audit rules 626)included in receipt entry ordering data 624 to reorder receipt entriesof digital receipt 632.

Through either of express instructions or defined audit priorities (in asubset of audit rules 626) a merchant or retailer can indicate thatitems are to be ordered by bulkiness. If item 634B is the bulkiest itemon digital receipt 632, reordering module 608 can reorder entry 633B fordisplay with increased prominence. If item 634C is the second bulkiestitem, reordering module 608 can reorder entry 633C for display withincreased prominence but somewhat less prominence than entry 634B. Ifitem 634D is less bulky than item 634C, reordering module 608 canreorder entry 633D for display with less prominence that entry 633C (andpossibly with less prominence than one or more other receipts entries ofdigital receipt 632). If item 634A is less bulky than item 634D,reordering module 608 can reorder entry 633A for display with lessprominence that entry 633D (and possibly with less prominence than oneor more other receipts entries of digital receipt 632).

In other embodiments, reordering module 608 can reorder digital receiptentries by profit margin, likelihood of items being stolen, etc.Reordering module 608 can refer to an item database (e.g., the itemdatabase used by POS systems at location 601) to access itemcharacteristics for items listed on a digital receipt.

Method 700 includes displaying the reordered receipt entries during thein-store audit so as to increase the likelihood of items with thespecified characteristics being expressly validated during the in-storeaudit (711). For example, auditor mobile device 603 can displayreordered entries from digital receipt 632 at display 606. The reorderedentries can be displayed in a list format with the first ordered entryat the top and followed by other entries in descending order. Forexample, entry 633B can be displayed at the top of the list at display606. Entry 633C can be displayed directly below entry 633B on the listat display 406. Entry 633D can be displayed one or more entries belowentry 633C on the list at display 406. Entry 633A can be display one ormore entries below entry 633D. One or more other entries can bedisplayed below entry 633A on the list at display 606.

Reordered entries from digital receipt can be displayed at display 606during an in-store audit of the customer in possession of one or more ofitems: 634A, 634C, and 634D. A human auditor can refer to display 606during the in-store audit of the customer. The human auditor can checkif the customer is in possession of any items not listed in digitalreceipt 632 (e.g., the customer is attempting to steal an item). Thehuman auditor can also check if the customer lacks possession of anyitems listed in digital receipt 632 (e.g., the customer left an item ata checkout lane). Since receipt entries for higher importance items aredisplayed nearer to the top of display 606, there is increasedlikelihood that the human auditor expressly validates these higherimportance items.

In other embodiments, the prominence of displayed digital receiptentries can be increased or decreased by varying font size, varying fontcolor, varying location on display 606, etc.

During an audit or when an audit is complete, the human auditor canindicate that they are satisfied with the outcome of the audit. Forexample, the human auditor can indicate that one or more items in acustomer's possession where audited and found to be listed on thecustomer's receipt. When a human auditor is satisfied with the outcomeof an audit, the human auditor can indicate to auditor mobile device 603that a transaction was satisfactorily audited.

On the other hand, during an audit or when an audit is complete, thehuman auditor can indicate that they are not satisfied with audit. Forexample, the human auditor may find one or more items in a customer'spossession that are not listed on the customer's receipt. When a humanauditor is not satisfied with an audit, the human auditor can indicateto auditor mobile device 603 that there is a problem with the auditor.Alternately, the human auditor can call other employees to assist. Forexample, an unsatisfactory audit can be escalated to more senior stafffor performance of other measures, such as, for example, reviewingsecurity footage.

FIGS. 8A and 8B illustrates an example computer architecture 800 thatfacilitates reordering and locating digital receipt data for use in anin-store audit. Referring to FIGS. 8A and 8B, computer architecture 800includes POS systems 802A-802J, auditor mobile device 803, receiptapplication server 821, and customer mobile device 823. Each of thedepicted systems, servers, and devices as well as their respectivecomponents can be connected to one another over (or be part of) anetwork, such as, for example, a PAN, a LAN, a WAN, and even theInternet. Accordingly, each of the depicted components as well as anyother connected computer systems and their components, can createmessage related data and exchange message related data (e.g., near fieldcommunication (NFC) payloads, Bluetooth packets, Internet Protocol (IP)datagrams and other higher layer protocols that utilize IP datagrams,such as, Transmission Control Protocol (TCP), Hypertext TransferProtocol (HTTP), Simple Mail Transfer Protocol (SMTP), etc.) over thenetwork.

POS systems 802A-802J, auditor mobile device 803, and receiptapplication server 821 can be commonly owned by a merchant or retailerthat operates a chain of stores. Location 801 can be a physical storelocation for the merchant or retailer. The merchant or retailer can alsohave one or more other physical store locations (not depicted in FIG.8). Location 801 and any other locations can be geographically diverselocations, such as, for example, in different cities, states, orcountries. The ellipses before, between, and after POS systems 802A-802Jrepresent that one or more additional POS systems can be included atlocation 801.

Each POS system, including POS systems 802A-802J can be physicallylocated at a checkout lane. Each POS system, including POS systems802A-802J can include a transaction processor, communication modules andadapters, and I/O peripherals.

Generally, a transaction processor is configured to manage salestransactions for a POS system. The transaction processor can receiveinput from I/O peripherals to open a sales transaction, collect digitalreceipt data (e.g., date, time, item, and cost data, etc.) for the salestransaction, and close the sales transaction. An item database can storeitem data for items sold by a retailer or merchant. For example, an itemdatabase can store item description data, item cost data, item size(bulkiness) data, item profit margin data, item theft statistics (howlikely is the item to be stolen), etc. for a plurality of items. Digitalreceipt data for an item (e.g., item description and item cost) can beretrieved from the item database in response to scanning a barcode on(or otherwise identifying) the item. Other item data can be usedinternally by the merchant or retailer but not necessarily for thegeneration of digital receipts.

I/O peripherals can include one or more of: a monitor (e.g., acashier-facing monitor), one or more input devices (e.g., scanners,keyboards, scales, or the like), one or more payment devices (e.g., cashdrawers, card readers, etc.) for receiving or returning payments, andone or more output devices (e.g., customer-facing display or monitor,receipt printer, etc.).

Communication modules and adapters can include wired and/or wirelessnetworking components for connecting the POS system with a network, suchas, for example, a Wi-Fi and/or wired Ethernet network, that facilitatesfurther connections (e.g., to the Internet).

Accordingly, when a sales transaction is closed, a POS system in aparticular location can use communication modules and adapters to senddigital receipt data to receipt application server 821. For example, POSsystems in location 801 can send digital receipt data to receiptapplication server 821. More particularly, POS system 802J can sendreceipt data 831, including entries 833A, 833B, 833C, etc. for items834A, 834B, 834C, etc. respectively, to receipt application server 821.Likewise, other POS systems at location 801 (e.g., POS system 802A) cansend receipt data to receipt application server 821.

Receipt database 822 can receive digital receipt data from POS systemsat various different store locations, including location 801. Receiptdatabase 822 can formulate digital receipts from received receipt data.Formulated digital receipts can include entries for items included incorresponding digital receipt data (but potentially in a differentformat, for example, a format deliverable to mobile devices). Receiptdatabase 822 can store formulated digital receipts in receipt database822. For example, receipt application server 821 can formulate and storedigital receipts 832 from digital receipt data 831. Receipt applicationserver 821 can also formulate other digital receipts 828 for otherreceipt data 827 (e.g., digital receipt data from other storelocations). Receipt application server 821 can store digital receipts832 and other receipts 828 in receipt database 822.

As such, in some embodiments, receipt data server 821 is part of abackend system that receives receipt data from a plurality of POSsystems distributed throughout different geographic locations. Theplurality of POS systems and the backend system can be part of acommonly owned and/or controlled corporate network infrastructure.

Subsequent to storing digital receipts, receipt application server 821can send stored digital receipts to customer mobile devices, such as,for example, smartphones and/or tablets. Receipt application server 821can send digital receipts to a mobile device in response to a requestand/or in accordance with configured settings. For example, in responseto a request for receipts from customer mobile device 823, receiptapplication server 821 can send digital receipt 832 to customer mobiledevice 823.

Alternately or in combination, receipt application server 821 canreorder receipt entries in a digital receipt in accordance with auditrules. Receipt application server 821 includes reordering module 808.Reordering module 808 is configured to reorder receipt entries of adigital receipt in accordance with auditing rules.

For example, reordering module 808 can refer to audit rules 826 todetermine how entries from digital receipts in receipt database 822(e.g., digital receipt 832 and other digital receipts 828) are to bereordered for presentation at an auditor mobile device. Audit rules canindicate how to reorder entries of a digital receipt for display basedon items characteristics. For example, audit rules 826 can indicate thatitems with higher profit margins, larger (or bulkier) items, items thatare more likely to be stolen, etc. are to be presented more prominentlyat a display. Reordered entries from digital receipts can then be sentto auditor mobile devices for display during in-store audits (e.g.,auditing a customer's possessed merchandise as they leave a physicalstore location).

Receipt application server 821 can send reordered receipt entries tozero or more auditor devices, such as, for example, auditor mobiledevice 803, in accordance with audit settings 824. Sending reorderedreceipt entries from receipt application server 821 to zero or moreauditor devices can involve push or polled mechanisms. Receiptapplication server 821 can send reordered receipt entries in a web ornative view. Audit settings 824 can indicate how and when to deliverydigital receipts to a merchant's or retailer's store locations for usein conducting customer audits. In some embodiments, POS systems attach alocation identifier to digital receipt data sent to receipt applicationserver 821. Audit settings 824 can include mappings between auditormobile devices and location identifiers. Receipt application server 821can use the mappings to delivery reordered receipt entries back to anauditor mobile device at the same location where a sales transactionoccurred.

For example, POS system 802J can attach a location identifier forlocation 801 to digital receipt data 831. Audit settings 824 can includea mapping between the location identifier and auditor mobile device 803(an auditor mobile device for location 801). Receipt application server821 can use the mapping to send corresponding reordered receipt entries(e.g., reordered receipt entries 876) back to auditor mobile device 803.Audit settings 824 can also include mappings between locationidentifiers and auditor mobile devices in other locations (e.g., storelocations that sent other digital receipt data 827). Receipt applicationserver 821 can use the mappings to send corresponding reordered receiptentries back to other auditor mobile devices.

As depicted, auditor mobile device 803 further includes receipt locatormodule 804, display 806, and cache 607. In general, an auditor mobiledevice 803 can receive reordered receipt entries and cache reorderedreceipt entries for using conducting customer audits. For example,auditor mobile device 803 can cache reordered receipt entries receivedfrom receipt application server 821 in cache 807 (e.g., system memory, aflash drive, or other storage).

Auditor mobile device 803 can cache reordered receipt entries inaccordance with a caching policy for a specified time period before thereordered receipt entries are removed. The caching policy can beconfigured so that there is a high likelihood of receipt entries for asales transaction still being cached when a customer that participatedin the sales transaction reaches a location where an audit is to occur.The caching policy can also be configured so that a portion of cacheremains available for new reordered receipt entries. In someembodiments, the specified time period is in a range from 5-30 minutes.

A receipt locator module at an auditor mobile device can locatereordered receipt entries from within cache based on one or moreidentified items. For example, a human auditor can scan a barcode or keyin information for one more items in a customer's possession. Thereceipt locator module can search the cache to locate a reorderedreceipt entries that includes (matches) an entry for each of the one ormore items. Matching one or more identified items to one or more entriesincluded in reordered receipt entries provides some degree of certaintythat located receipt entries correspond to the customer. For example,receipt locator module 804 can search cache 807 to locate reorderedreceipt entries that include entries for items identified at auditormobile device 803.

Located reordered receipt entries can then be presented at a displaydevice for use in conducting an in-store audit. A human auditor canrefer to the presented entries to audit (e.g., matched and/oradditional) items in the customer's possession. For example, reorderedreceipt entries located in cache 807 can be presented at display 806. Ahuman auditor at location 801 can refer to the entries presented atdisplay 806 to perform an in-store audit of a customer. During displayof digital receipt entries at display 806, some parts of a digitalreceipt can be hidden from the human auditor's view to ensure customerprivacy.

The human auditor may also chose to apply different audit prioritiesafter viewing reordered receipt entries. For example, if receipt entrieswhere initially ordered by likelihood of theft, the human auditor maychoose to reorder receipt entries based on profit margin or bulk.

Prior to use of auditor mobile device 803 by a human auditor, the humanauditor can authenticate on auditor mobile device 803. The human auditorcan then select a store location, for example, based on geolocation.

FIGS. 9A and 9B illustrates a flow chart of an example method forreordering and locating digital receipt data for use in an in-storeaudit. Method 900 will be described with respect to the components anddata of computer architecture 800.

Method 900 includes receiving digital receipt data for a salestransaction conducted at a Point-Of-Sale (POS) system, the Point-Of-Sale(POS) system in a store location selected from among the one or morestore locations, the digital receipt data containing a receipt entry foreach of one or more items purchased by a customer in the salestransaction (901). For example, receipt application server 821 canreceive digital receipt data 831 for a sales transaction conducted atPOS system 802J. Digital receipt data 831 contains entries 833A, 834B,834C, etc. for items 834A, 834B, 834C, etc. purchased in the salestransaction by a customer at location 801.

Method 900 includes generating a digital receipt for the salestransaction, the digital receipt generated from the digital receiptdata, the digital receipt containing the receipt entry for each of theone or more purchased items, the digital receipt providing proof of thesales transaction, the digital receipt for delivery to a customer mobiledevice associated with the customer (902). For example, receiptapplication server 821 can generate digital receipt 832 from digitalreceipt data 831. Digital receipt 832 provides proof of the salestransaction at POS system 802J. Digital receipt 832 can be delivered toa customer mobile device associated with the customer.

Method 900 includes receiving an indication that the sales transactionis to be audited in the store location (903). For example, receiptapplication server 821 can receive an indication that the salestransactions corresponding to digital receipt 832 is to be audited. Insome embodiments, receipt application server 821 is configured to auditall sales transactions. In other embodiments, receipt application server821 refers to audit settings 824 to determine if a sales transaction isto be audited. Audit settings 824 can indicate that digital receiptswith entries for specified items (e.g., higher profit margin items,bulkier items, items that are more likely to be stolen, etc.) are toaudited, can indicate that digital receipts are to be randomly audited,can indicate that digital receipts are to be audited at specified datesand/or times, can indicate that digital receipts are to be audited basedon the number of entries in a digital receipt, etc.

Method 900 includes referring to audit rules, the audit rules definingan audit priority for each of the one or more purchased items based oncharacteristics of each of the one or more purchased items, an auditpriority for an item indicating an importance of expressly validatingthe item during the in-store audit (904). For example, reordering module808 can refer to audit rules 826. Audit rules 826 represent a merchantor retailer defined audit priority for each of items 834A, 834B, 834C,etc. based on characteristics of each of items 834A, 834B, 834C, etc.For example, audit rules 826 can indicate that the merchant or retailerhas placed increased importance on expressly validating items withspecified characteristics, such as, for example, higher profit marginsitems, bulkier items, items that are more likely to be stolen, etc.during an in-store audit.

Method 900 includes reordering the receipt entries of the digitalreceipt based on the defined audit priority for each of the one or moreitems (905). For example, reordering module 808 can reorder entries833A, 833B, 833C, etc. of digital receipt 832 into reordered receiptentries 876 in accordance with the defined audit priority for each ofitems 834A, 834B, 834C, etc. Items 834A, 834B, 834C, etc. can bereordered to increase the likelihood of items with higher indicatedimportance being expressly validated during the in-store audit.Reordering receipt entries can include changing the original ordering ofentries in a digital receipt. An original (or default) ordering can bethe order in which items where scanned at the time of the salestransactions (e.g., the sales transaction for which digital receipt 832was generated).

For example, it may be that a merchant or retailer has defined auditrules 826 to indicate that items are to be ordered by likelihood ofbeing stolen. If item 834B is the most likely item on digital receipt832 to be stolen, reordering module 808 can order entry 833B for displaywith increased prominence. If item 834C is a moderately likely item ondigital receipt 832 to be stolen, reordering module 808 can order entry833C for display with an appropriate level prominence but with lessprominence than entry 833B (and possibly with less prominence than oneor more other entries). If item 834A is a less likely item on digitalreceipt 832 to be stolen, reordering module 808 can order entry 833A fordisplay with an appropriate level prominence but with less prominencethan entry 833C (and possibly with less prominence than one or moreother entries). Reordering module 808 can order other entries on digitalreceipt 832 for display prominence concomitant with correspondinglikelihoods of being stolen.

In other embodiments, reordering module 808 can reorder digital receiptentries by profit margin, item bulkiness, etc. Reordering module 808 canrefer to an item database (e.g., the item database used by POS systemsat location 801) to access item characteristics for items listed on adigital receipt.

Method 900 includes sending the reordered receipt entries to an auditormobile device used for in-store audits at the store location, thereordered receipt entries displayable at the auditor mobile device so asto increase the likelihood of expressly validating items with higherindicated importance during the in-store audit (906). For example,receipt application server 821 can send reordered receipt entries 876 toauditor mobile device 803. Prior to or after sending reordered receiptentries 876, receipt application server 821 can also send otherreordered receipt entries 829 (as well as other reordered receiptentries for sales transactions conducted at location 801) to auditormobile device 803.

Method 900 includes receiving reordered receipt entries for a digitalreceipt from the receipt application server, the digital receiptcorresponding to a sales transaction conducted at the store location,each of the reordered receipt entries corresponding to an item purchasedby a customer in the sales transaction, the reordered receipt entriesreordered from a default order of the digital receipt in accordance withaudit rules, the audit rules defining an audit priority for items basedon characteristics of the items, an audit priority for an itemindicating an importance of expressly validating the item during anin-store audit (907). For example, auditor mobile device 803 can receivereordered receipt entries 876 from receipt application server 821. Priorto or after receiving reordered receipt entries 876, receipt applicationserver 421 can also receive other reordered receipt entries 829 (as wellas other reordered receipt entries for sales transactions conducted atlocation 801) from receipt application server 821.

Method 900 includes caching the reordered receipt entries for thedigital receipt at the auditor mobile device (908). For example, auditormobile device 803 can cache reordered receipt entries 876 in cache 807.Prior to or after caching reordered receipt entries 876, auditor mobiledevice 803 can also cache other reordered receipt entries 876 (as wellas other reordered receipt entries for sales transactions conducted atlocation 801) in cache 807.

Method 900 includes subsequent to caching the reordered receipt entries,receiving an indication that a customer is in possession of one or moreitems sold at the store location and is in an auditing area within thestore location (909). For example, receipt locator module 804 canreceive one or more of indications 871 and 872 indicating that acustomer is in possession of items 834B and/or 834A. Indications 871 and872 can be received from a peripheral device, such as, for example, abarcode scanner or keyboard, connected to auditor mobile device 803. Forexample, a human auditor can scan a barcode on an item in a customer'spossession (e.g., in a shopping cart).

Auditor mobile device 803 can be stationed at a specified audit areawithin location 801 (e.g., somewhere in a path between checkout lanesand a store exit). Thus, when an item is indicated to auditor mobiledevice 803, auditor mobile device 803 views the customer possessing theitem to be within the specified audit area.

Method 900 includes using the indication of the possessed one or moreitems to identify the reordered receipt entries, from among one or morereordered receipt entries cached at the auditor mobile device, for usein an in-store audit, identification of the reordered receipt entriesincluding detecting that receipt entries for the possessed one or moreitems are included in the reordered receipt entries (910). For example,receipt locator module 804 can use one or more of: indications 871 and872 to identify reordered receipt entries 876, from among reorderedreceipt entries cached in cache 807, for use in an in-store audit atlocation 801. To identify reordered receipt entries 876, receipt locatormodule 804 can detect that reordered receipt entries 876 includes one ormore of: entry 833B for item 834B and entry 833A for item 834A.

That is, one or more items identified in a customer's possession (byindications 871 and 872) are listed in cached reordered receipt entries876. As such, auditor mobile device 803 has some level of certainty thatcached reordered receipt entries 876 correspond to the customer's salestransaction and that the cached reordered receipt entries 876 list otherpurchased items that are to be in the customer's possession.

Method 900 includes displaying the reordered receipt entries during thein-store audit so as to increase the likelihood of items with higherindicated importance being expressly validated during the in-store audit(911). For example, auditor mobile device 803 can display reorderedentries 876 at display 806. The reordered entries can be displayed in alist format with the first ordered entry at the top and followed byother entries in descending order. For example, entry 833B can bedisplayed at the top of the list at display 806. Entry 833C can bedisplayed one or more entries below entry 833B on the list at display806. Entry 833A can be displayed one or more entries below entry 833C.One or more other entries can be displayed below entry 833A on the listat display 806.

Reordered receipt entries 876 can be displayed at display 806 during anin-store audit of the customer in possession of one or more of items:834A and 834B. A human auditor can refer to display 806 during thein-store audit of the customer. The human auditor can check if thecustomer is in possession of any items not listed in reordered receiptentries 876, and thus not listed in digital receipt 832 (e.g., thecustomer is attempting to steal an item). The human auditor can alsocheck if the customer lacks possession of any items listed in reorderedreceipt data 876, and thus listed in digital receipt 832 (e.g., thecustomer left an item at a checkout lane). Since receipt entries forhigher importance items are displayed nearer to the top of display 806,there is increased likelihood that the human auditor expressly validatesthese higher importance items.

In other embodiments, the prominence of displayed digital receiptentries can be increased or decreased by varying font size, varying fontcolor, varying location on display 806, etc.

During an audit or when an audit is complete, the human auditor canindicate that they are satisfied with the outcome of the audit. Forexample, the human auditor can indicate that one or more items in acustomer's possession where audited and found to be listed on thecustomer's receipt. When a human auditor is satisfied with the outcomeof an audit, the human auditor can indicate to auditor mobile device 803that a transaction was satisfactorily audited.

On the other hand, during an audit or when an audit is complete, thehuman auditor can indicate that they are not satisfied with audit. Forexample, the human auditor may find one or more items in a customer'spossession that are not listed on the customer's receipt. When a humanauditor is not satisfied with an audit, the human auditor can indicateto auditor mobile device 803 that there is a problem with the auditor.Alternately, the human auditor can call other employees to assist. Forexample, an unsatisfactory audit can be escalated to more senior stafffor performance of other measures, such as, for example, reviewingsecurity footage.

FIG. 10 illustrates an example schematic block diagram of apoint-of-sale (POS) system 1000. In some embodiments, the hardware,software, or hardware and software of POS system 1000 may be configuredto implement one or more methods in accordance with the presentinvention. For example, POS system 1000 may be manufactured, programmed,modified, or upgraded to support transferring digital receipt data tomobile devices. Any of POS systems 202A-202N, 212A-212N, 402A-402N,602A-602C, and 802A-802J_can be a POS system similar to POS system 1000.

POS system 1000 can include various components. In some embodiments, POSsystem 1000 includes a central or primary computer 1012, a monitor 1014(e.g., a cashier-facing monitor 1014), one or more input devices 1016(e.g., scanners 1016 a, keyboards 1016 b, scales, or the like), one ormore payment devices 1018 (e.g., cash drawers 1018 a, card readers 1018b) for receiving or returning payments, one or more output devices 1020(e.g., customer-facing display 1020 a or monitor 1020 a, receipt printer1020 b), or the like or combinations or sub-combinations thereof, andNFC module 1022, such as, for example, an NFC dongle.

Computer 1012 may form the backbone of POS system 1010. Other components1016, 1018, 1020, 1022 forming part of a POS system 1010 can communicatewith computer 1012. Input devices 1016 and certain payment devices 1018can feed data and commands to computer 1012 for processing orimplementation. For example, scanner 1016 a can pass data communicatingthe identity of one or more items to be purchased, returned, or the liketo a computer 1012. Similarly, card reader 1018 b can pass paymentinformation to computer 1012.

On the other hand, output devices 1020 and certain payment devices 1018can follow or implement commands issued by computer 1012. For example,cash drawer 1018 a may open in accordance with the commands of computer1012. Similarly, customer-facing display 1020 a and receipt printer 820b can display or output data or information as instructed by computer1012.

In some embodiments, in addition to handling consumer transactions(e.g., purchases, returns), POS system 1000 can provide or supportcertain “back office” functionality. For example, POS system 1000 canprovide or support inventory control, purchasing, receiving andtransferring products, or the like. POS system 1000 can also store salesand customer information for reporting purposes, marketing purposes,receivables management, trend analysis, cost analysis, price analysis,profit analysis, or the like. If desired or necessary, POS system 1000can include an accounting interface to pass certain information to oneor more in-house or independent accounting applications.

In some embodiments, POS system 1000 operates substantiallyindependently, as a stand-alone unit. Alternately, POS system 1000 maybe one of several POS systems 1000 forming the front line of a largersystem. FIG. 11 illustrates an example schematic block diagram of anetwork 1100 of point-of-sale (POS) systems 1000. For example, multiplePOS systems 1000 may operate at a particular location 1122 (e.g., withina retail, brick-and-mortar store). In such embodiments, the various POSsystems 1000 may be interconnected via LAN 1124. LAN 1124 may alsoconnect the POS systems 1000 to a local server 1126.

Local server 1126 can support the operation of the associated POSsystems 1000. For example, a server 1126 may provide a centralrepository from which certain data needed by the associated POS systems1000 may be stored, indexed, accessed, or the like. Server 1126 canserve certain software to one or more POS systems 1000. In certainembodiments, a POS system 800 can offload certain tasks, computations,verifications, or the like to server 1126.

Alternatively, or in addition thereto, server 1126 can support certainback office functionality. For example, server 1126 can receive andcompile (e.g., within an associated database 1128) data from the variousassociated POS systems 1000 to provide or support inventory control,purchasing, receiving and transferring products, or the like. Server1126 can also receive and compile sales and customer information forreporting purposes, marketing purposes, receivables management, trendanalysis, cost analysis, price analysis, profit analysis, or the like.

In some embodiments, one or more POS systems 1000 and/or servers 1126corresponding to a particular location 1122 can communicate with oraccess one or more remote computers or resources via one or more networkdevices 1130. For example, a network device 1130 can enable a POS system1000 to contact outside resources and verify the payment credentials(e.g., credit card information) provided by a customer. A network device1130 can comprise a modem, router, or the like.

In selected embodiments, POS systems 1000 operate within anenterprise-wide system 1131 comprising multiple locations 1122 (e.g.,branches 1122 or stores 1122). In such embodiments, each location 1122may have one or more POS systems 1000, local servers 1126, localdatabases 1128, network devices 1130, or the like or combinations orsub-combinations thereof connected by a computer network (e.g., a LAN1124). It may be that any of data receipt servers 221, 421, 621, and 821are included in and/or include the functionality of a local server 1126.

Additionally, each such location 1122 may be configured to interact withone or more supervisory systems 1132. For example, multiple branchlocations 1122 may report to an associated “headquarters” location orsystem. It may be that any of data receipt servers 221, 421, 621, and821 are included in and/or include the functionality of a supervisorysystem 1132.

A supervisory system 1132 can include one or more supervisory servers934, databases 1136, workstations 1138, network devices 1140, or thelike or combinations or sub-combinations thereof. The various componentsof a supervisory system 1132 can be interconnected via a computernetwork (e.g., a LAN 1142). In selected embodiments, a supervisorysystem 1132 includes one or more supervisory servers 1134 providing acentral repository from which certain data needed by the one or more POSsystems 1100 or local servers 926 may be stored, indexed, accessed, orthe like.

Alternatively, or in addition thereto, a supervisory server 934 canreceive and compile (e.g., within an associated database 1136) data fromthe various associated POS systems 1000 or local servers 1126 to provideor support inventory control, purchasing, receiving and transferringproducts, or the like. A supervisory server 1134 may also receive andcompile sales and customer information for reporting purposes, marketingpurposes, receivables management, trend analysis, cost analysis, priceanalysis, profit analysis, or the like.

A supervisory system 1132 can be connected to one or more associatedlocations 1122 or branches 1122 in via any suitable computer network1144 (e.g., WAN 1144). For example, in selected embodiments, one or morelocations 1122 can connect to a supervisor system 1132 via the Internet.Communication over such a network 1144 can follow any suitable protocolor security scheme. For example, communication may utilize the FileTransfer Protocol (FTP), a virtual private network (VPN), intranet, orthe like.

Although the components and modules illustrated herein are shown anddescribed in a particular arrangement, the arrangement of components andmodules may be altered to process data in a different manner. In otherembodiments, one or more additional components or modules may be addedto the described systems, and one or more components or modules may beremoved from the described systems. Alternate embodiments may combinetwo or more of the described components or modules into a singlecomponent or module.

The foregoing description has been presented for the purposes ofillustration and description. It is not intended to be exhaustive or tolimit the invention to the precise form disclosed. Many modificationsand variations are possible in light of the above teaching. Further, itshould be noted that any or all of the aforementioned alternateembodiments may be used in any combination desired to form additionalhybrid embodiments of the invention.

Further, although specific embodiments of the invention have beendescribed and illustrated, the invention is not to be limited to thespecific forms or arrangements of parts so described and illustrated.The scope of the invention is to be defined by the claims appendedhereto, any future claims submitted here and in different applications,and their equivalents.

What is claimed:
 1. At a receipt application server for a merchant, thereceipt preferences database including one or more processors and systemmemory, the receipt application server connected to one or morePoint-Of-Sale (POS) systems and one or more auditor mobile devices ateach of one or more store locations for the merchant, the receiptapplication server configured to manage a receipt database for themerchant, a method for reordering digital receipt data for using in anin-store audit, the method comprising: receiving digital receipt datafor a sales transaction conducted at a Point-Of-Sale (POS) system, thePoint-Of-Sale (POS) system in a store location selected from among theone or more store locations, the digital receipt data containing areceipt entry for each of one or more items purchased by a customer inthe sales transaction; generating a digital receipt for the salestransaction, the digital receipt generated from the digital receiptdata, the digital receipt containing the receipt entry for each of theone or more purchased items, the digital receipt providing proof of thesales transaction, the digital receipt for delivery to a customer mobiledevice associated with the customer; receiving an indication that thesales transaction is to be audited in the store location; referring toaudit rules, the audit rules defining an audit priority for each of theone or more purchased items based on characteristics of each of the oneor more purchased items, an audit priority for an item indicating animportance of expressly validating the item during the in-store audit;reordering the receipt entries of the digital receipt based on thedefined audit priority for each of the one or more items; and sendingthe reordered receipt entries to an auditor mobile device used forin-store audits at the store location, the reordered receipt entriesdisplayable at the auditor mobile device so as to increase thelikelihood of expressly validating items with higher indicatedimportance during the in-store audit.
 2. The method of claim 1, whereinreceiving digital receipt data for a sales transaction conducted at aPoint-Of-Sale (POS) system comprises receiving an item price and itemdescription for each of the one or more items.
 3. The method of claim 1,wherein receiving an indication that the sales transaction is to beaudited comprises referring to audit settings that indicate how and whendeliver digital receipts to store locations for use in conductingcustomer audits.
 4. The method of claim 1, further comprising subsequentto generating the digital receipt delivering the digital receipt to thecustomer mobile device associated with the customer.
 5. The method ofclaim 1, wherein referring to audit rules comprises referring to auditrules that define an increased level of importance for expresslyvalidating one or more of: higher profit margin items, bulkier items,and items that are more likely to be stolen, during the in-store audit.6. The method of claim 1, wherein reordering the receipt entries of thedigital receipt comprises reordering the receipt entries based on itemprofit margin.
 7. The method of claim 1, wherein reordering the receiptentries of the digital receipt comprises reordering the receipt entriesbased on item bulkiness.
 8. The method of claim 1, wherein reorderingthe receipt entries of the digital receipt comprises reordering thereceipt entries based item risk of theft.
 9. At an auditor mobile devicefor a merchant, the auditor mobile device including one or moreprocessors and system memory, the auditor mobile device at a storelocation for the merchant, the auditor mobile device connected to areceipt application server, the receipt application server configured tomanage a receipt database for the merchant, a method for locatingdigital receipt data for using in an in-store audit, the methodcomprising: receiving reordered receipt entries for a digital receiptfrom the receipt application server, the digital receipt correspondingto a sales transaction conducted at the store location, each of thereordered receipt entries corresponding to an item purchased by acustomer in the sales transaction, the reordered receipt entriesreordered from a default order of the digital receipt in accordance withaudit rules, the audit rules defining an audit priority for items basedon characteristics of the items, an audit priority for an itemindicating an importance of expressly validating the item during anin-store audit; caching the reordered receipt entries for the digitalreceipt at the auditor mobile device; subsequent to caching thereordered receipt entries, receiving an indication that a customer is inpossession of one or more items sold at the store location and is in anauditing area within the store location; using the indication of thepossessed one or more items to identify the reordered receipt entries,from among one or more reordered receipt entries cached at the auditormobile device, for use in an in-store audit, identification of thereordered receipt entries including detecting that receipt entries forthe possessed one or more items are included in the reordered receiptentries; and displaying the reordered receipt entries during thein-store audit so as to increase the likelihood of items with higherindicated importance being expressly validated during the in-storeaudit.
 10. The method of claim 9, wherein each receipt entry includes anitem price and an item description for an item purchases in a salestransaction.
 11. The method of claim 9, wherein caching the reorderedreceipt entries for the digital receipt comprises caching the reorderedreceipt entries in accordance with a caching policy.
 12. The method ofclaim 9, wherein receiving an indication that a customer is inpossession of one or more items sold at the store location and is in anauditing area within the store location comprises receiving input from abarcode scanner in the auditing area that identifies one of the one ormore items.
 13. The method of claim 9, wherein displaying the reorderedreceipt entries during the in-store audit comprises displaying receiptentries for higher profit margin items more prominently than receiptentries for lower profit margin items.
 14. The method of claim 9,wherein displaying the reordered receipt entries during the in-storeaudit comprises displaying receipt entries for more bulky items moreprominently than receipt entries for less bulky items.
 15. The method ofclaim 9, wherein displaying the reordered receipt entries during thein-store audit comprises displaying receipt entries for items havingincreased risk of being stolen more prominently than receipt entries foritems having decreased risk of being stolen.
 16. A system for reorderingand locating digital receipt data for use in an in-store audit, thesystem comprising: a Point-Of-Sale (POS) computer system, a receiptapplication server, and an auditor mobile device, the Point-Of-Sale(POS) computer system and the auditor mobile device at a store location,the Point-Of-Sale (POS) computer system comprising: one or moreprocessors; system memory; one or more computer storage media havingstored thereon computer-executable instructions that, when executed,cause the Point-Of-Sale (POS) computer system to: open a salestransaction; collect digital receipt data for the sales transaction, thedigital receipt data containing a receipt entry for each of one or moreitems purchased by a customer in the sales transaction; close the salestransaction; and send the digital receipt data for the sales transactionto the receipt application server; the receipt application servercomprising: one or more processors; system memory; one or more computerstorage media having stored thereon computer-executable instructionsthat, when executed, cause the receipt application server to: receivethe digital receipt data for the sales transaction from thePoint-Of-Sale (POS) system; generate a digital receipt for the salestransaction, the digital receipt generated from the digital receiptdata, the digital receipt containing the receipt entry for each of theone or more purchased items, the digital receipt providing proof of thesales transaction; receive an indication that the sales transaction isto be audited in the store location; refer to audit rules, the auditrules defining an audit priority for each of the one or more purchaseditems based on characteristics of each of the one or more purchaseditems, an audit priority for an item indicating an importance ofexpressly validating the item during an in-store audit; reorder thereceipt entries of the digital receipt based on the defined auditpriority for each of the one or more items; and send the reorderedreceipt entries to the auditor mobile device; and the auditor mobiledevice comprising: one or more processors; system memory; one or morecomputer storage media having stored thereon computer-executableinstructions that, when executed, cause the auditor mobile device to:receive the reordered receipt entries from the receipt applicationserver; cache the reordered receipt entries for the digital receipt;subsequent to caching the reordered receipt entries, receive anindication that the customer is in possession at least one of the one ormore items; using the indication of the possessed at least one item toidentify the reordered receipt entries, from among one or more reorderedreceipt entries cached at the auditor mobile device, for use in anin-store audit; and display the reordered receipt entries during thein-store audit to increase the likelihood of items with higher indicatedimportance being expressly validated during the in-store audit.
 17. Thesystem of claim 16, wherein computer-executable instructions that, whenexecuted, cause the receipt application server to audit rules comprisescomputer-executable instructions that, when executed, cause the receiptapplication server to refer to audit rules that define an increasedlevel of importance for expressly validating one or more of: higherprofit margin items, bulkier items, and items that are more likely to bestolen, during the in-store audit.
 18. The system of claim 16, whereincomputer-executable instructions that, when executed, cause the receiptapplication server to reorder the receipt entries of the digital receiptcomprise computer-executable instructions that, when executed, cause thereceipt application server to reorder the receipt entries based on oneof: item profit margin, item bulkiness, and item risk of theft.
 19. Thesystem of claim 16, wherein computer-executable instructions that, whenexecuted, cause the auditor mobile device to receive an indication thatthe customer is in possession of at least one of the one or more itemscomprise computer-executable instructions that, when executed, cause theauditor mobile device to receive input from a barcode scanner, thereceived input identifying the at least one of the one or more items.20. The system of claim 16, wherein computer-executable instructionsthat, when executed, cause the auditor mobile device to display thereordered receipt entries during the in-store audit comprisecomputer-executable instructions that, when executed, cause the auditormobile device to display receipt entries for one of: higher profitmargin items, more bulky items, or items having increased risk of beingstolen, more prominently than receipt entries for other items.